How pranayagrawal2116/abdm_yashfeen works
Sarita is a healthcare-record and ABDM integration backend, with M1-style patient/facility workflows and separate M2 and M3 integration flows. Users and ABDM callbacks enter through the Express application and API routes; the backend handles identity/linking, consent, and health-information transfer, with FHIR document construction and patient-data storage supporting those flows. M2 callback/consent and M3 consent paths are distinct. The README provides no architectural detail, and several subsystems are unsampled; those are included where the tree identifies them, without asserting unverified call relationships.
Main entry points: M2DataTransferManager.js M2 Data Transfer · M2ConsentManager.js M2 Consent Manager · app.js Express Application · routes M2 API Routes
Components 23
API and Linking
- Express Application
backend/app.js - M1 API Routes
backend/routes - HIP Linking
backend/controllers/hipLinkingController.js - Consent API
backend/controllers/consentController.js - Gateway Client
backend/services/gatewayService.js
ABDM M2
- M2 API Routes
backend/m2/routes - M2 Consent Manager
backend/m2/consent/M2ConsentManager.js - M2 Callback Manager
backend/m2/callbacks/M2CallbackManager.js - M2 Data Transfer
backend/m2/transfer/M2DataTransferManager.js - Health Information Requests
backend/m2/healthInformation/M2HealthInformationRequestManager.js - M2 Token Manager
backend/m2/tokens/M2TokenManager.js - M2 Encryption
backend/m2/encryption/M2EncryptionService.js
ABDM M3
- M3 API Routes
backend/m3/routes - M3 Consent Service
backend/m3/services/m3ConsentService.js - M3 Callback Controller
backend/m3/controllers/m3CallbackController.js - M3 Token Manager
backend/m3/tokens/M3TokenManager.js
Records and Persistence
- M2 Transactions
backend/m2/transactions/M2TransactionStore.js - FHIR Builders
backend/m2/fhir - M2 Patient Storage
backend/m2/storage/PatientStorageService.js - M3 Patient Storage
backend/m3/services/m3PatientStorageService.js - M3 Consent Store
backend/m3/store/M3ConsentStore.js
Other components
- Patient / Operator
- ABDM Gateway
Connections 28
- Patient / Operator → Express Application: sends requests
backend/app.js - Express Application → M1 API Routes: mounts routes
backend/app.js - Express Application → M2 API Routes: mounts routes
backend/app.js - Express Application → M3 API Routes: mounts routes
backend/app.js - M1 API Routes → HIP Linking: routes requests
- M1 API Routes → Consent API: routes requests
- HIP Linking → ABDM Gateway: posts link requests
backend/controllers/hipLinkingController.js - HIP Linking → M2 Consent Manager: registers link context
backend/controllers/hipLinkingController.js - Consent API → Gateway Client: uses gateway client
backend/controllers/consentController.js - Gateway Client → ABDM Gateway: fetches session token
backend/services/gatewayService.js - M2 API Routes → M2 Consent Manager: routes consent
- M2 API Routes → M2 Data Transfer: routes transfers
- M2 API Routes → M2 Patient Storage: routes storage
backend/m2/routes/patientStorageRoutes.js - M2 Callback Manager → M2 Consent Manager: dispatches callbacks
backend/m2/consent/M2ConsentManager.js - M2 Consent Manager → M2 Callback Manager: registers handlers
backend/m2/consent/M2ConsentManager.js - M2 Consent Manager → M2 Transactions: updates transactions
backend/m2/consent/M2ConsentManager.js - M2 Data Transfer → Health Information Requests: uses request manager
backend/m2/transfer/M2DataTransferManager.js - M2 Data Transfer → M2 Consent Manager: checks consent
backend/m2/transfer/M2DataTransferManager.js - M2 Data Transfer → M2 Token Manager: gets tokens
backend/m2/transfer/M2DataTransferManager.js - M2 Data Transfer → M2 Encryption: encrypts data
backend/m2/transfer/M2DataTransferManager.js - M2 Data Transfer → M2 Transactions: records transfers
backend/m2/transfer/M2DataTransferManager.js - M2 Data Transfer → FHIR Builders: builds FHIR bundles
backend/m2/transfer/M2DataTransferManager.js - M2 Token Manager → ABDM Gateway: requests gateway sessions
- M3 API Routes → M3 Callback Controller: routes callbacks
backend/m3/routes/m3CallbackRoutes.js - M3 Callback Controller → M3 Consent Service: uses consent service
backend/m3/controllers/m3CallbackController.js - M3 Callback Controller → M3 Consent Store: uses consent store
backend/m3/controllers/m3CallbackController.js - M3 Callback Controller → M3 Patient Storage: uses patient storage
backend/m3/controllers/m3CallbackController.js - M3 Token Manager → ABDM Gateway: fetches session token
backend/m3/tokens/M3TokenManager.js