skills.rest
leipold-us
leipold-usCOMMUNITY
Explore all skills by this author →
𝕏@leipoldGitHub

ssa-hit-architect

Provide SSA HIT domain knowledge for disability determination system integrations.

Updated Apr 8, 2026
Search Tags:#enterprise architecture#cef#ssa disability#health it integration#megahit#poms policy#medical evidence collection
One-click install
npx skills add https://github.com/leipold-us/ssa-disability-ea-skills --skill ssa-hit-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ssa-hit-architect
Source: https://github.com/leipold-us/ssa-disability-ea-skills/tree/main/ssa-hit-architect
Command: npx skills add https://github.com/leipold-us/ssa-disability-ea-skills --skill ssa-hit-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the knowledge gap for solution and segment architects working on SSA disability program integrations, providing authoritative, up-to-date domain knowledge of SSA's medical evidence collection ecosystem, legacy system constraints, and regulatory requirements that prevent non-compliant or non-functional solution designs.

Core Features & Use Cases

  • SSA Systems Reference: Detailed breakdown of core SSA HIT and case processing systems (MEGAHIT, EDCS, CEF, ERE, DCPS, eView) with their functions, integration relevance, and technical constraints.
  • Policy & Compliance Guidance: Critical POMS sections, SSA-827/e-827 authorization rules, accepted document format standards (CCDA, IHE XCA), and FedRAMP requirements to ensure solutions meet SSA's regulatory and technical guardrails.
  • Opportunity & Integration Matrix: Ten identified structural gaps in SSA's evidence collection workflow with specific integration touchpoints for solution plug-in, plus RFI context, market landscape (TEFCA, eHealth Exchange, key partners), and architect guidance for common integration scenarios (AI/NLP layers, identity resolution, record collection vendors).
  • Use Case: An architect designing an AI/NLP layer to process incoming medical records for SSA examiners can use this skill to identify the correct integration point (CEF → eView/DCPS), required FedRAMP impact levels, policy constraints around PDF/TIFF conversion, and mandatory human review gates for medical equivalence findings.

Quick Start

Use the ssa-hit-architect skill to map your proposed electronic health record integration solution to SSA's MEGAHIT, CEF, and DCPS system touchpoints and validate compliance with POMS policy and technical standards.

Frequently Asked Questions about ssa-hit-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate a health IT solution with SSA disability determination systems?▼

To integrate with SSA disability determination systems, you map your solution to core SSA HIT touchpoints like MEGAHIT, EDCS, CEF, and DCPS. The architecture must align with specific system functions, technical constraints, and evidence workflow integration points.

What POMS policy and technical standards are required for SSA medical evidence collection?▼

SSA medical evidence collection requires compliance with POMS policy sections, SSA-827 authorization rules, and technical standards like IHE XCA and CCDA. Solutions must also meet FedRAMP requirements and accepted document format specifications.

How does the CEF system connect to eView and DCPS for processing medical records?▼

The CEF system connects to eView and DCPS by routing collected medical evidence for examiner review. Architects designing AI or NLP layers must target this CEF to eView/DCPS pathway while enforcing mandatory human review gates for medical equivalence findings.

Do I need FedRAMP certification to build an SSA health IT integration solution?▼

Yes, building SSA health IT integration solutions requires FedRAMP compliance. Architects must identify the correct FedRAMP impact levels for their specific integration scenarios, record collection vendors, and identity resolution components.

What are the structural integration gaps in the SSA evidence workflow?▼

The SSA evidence workflow contains ten identified structural gaps offering specific integration touchpoints. Architects can use these opportunities to plug in AI processing layers, NLP solutions, or record collection vendors.

Can I use eHealth Exchange or TEFCA for SSA health IT integration?▼

Yes, eHealth Exchange and TEFCA are part of the SSA health IT vendor landscape. Architects can leverage these networks when designing integration solutions, provided they adhere to SSA technical standards and regulatory constraints.

Related Skills

Explore More Software Engineering Skills→
aks-buildsaks-builds
1

ihe-profiles

Provides IHE integration profile information including actors, transactions, and FHIR equivalents.

Community
Advanced
leipold-usleipold-us

ssa-disability-ea

Document SSA disability determination processes and POMS policy for architects.

Community
Advanced
kcc989kcc989

cloudflare-containers

Deploy and manage Docker containers on Cloudflare's global network with Wrangler.

Community
Advanced
aks-buildsaks-builds
1

tefca-hie

Guide technical and contractual integration with TEFCA health information exchange.

Community
Advanced