How cmsgov/bcda-app works
Main Components
a) API Layer Components:
• BCDA API Service (main API application)
• BCDA Worker Service (background job processor)
• SSAS (Security/Authentication Service)
• API Gateway/Router
b) Data Storage:
• PostgreSQL Database (primary data store)
• S3 Storage (for CCLF files and suppressions)
c) External Services:
• Blue Button API Integration
• AWS Services Integration
Key Architectural Elements
a) Service Boundaries:
• Authentication/authorization flow
• Job queue system between API and Worker
b) Data Flow Patterns:
• Claims data ingestion flow
• Authentication flow
• Job processing flow
• File storage and retrieval flow
Detailed Component Breakdown
API Service Components:
• Authentication (auth/)
• API Endpoints (api/v1/, api/v2/)
• FHIR Models (models/fhir/)
• Database Layer (models/postgres/)
• File Processors (cclf/)
Worker Service Components:
• Queue Management (queueing/)
• Job Processing (worker/)
• File Generation
• Data Export
Key Workflows to Highlight
a) Claims Data Processing:
CCLF Import → Database Storage → Job Queue → Worker Processing → File Generation → S3 Storage
b) API Request Flow:
Client → API Gateway → Auth Service → API Service → Database/Storage → Response
Deployment Context
• Container boundaries (using Docker)
• AWS service integration points
• Development vs. production components
This architecture reflects a modern, cloud-native application with clear separation of concerns, robust security, and scalable processing capabilities for handling Medicare claims data.