DentPal - CONNECT

Validate data retrieval, DTO mapping, encryption, and payload submission for both OpenDental and Sidexis systems.¶

This sub-task focuses on data extraction and verification only , without full backend authorization or production validation.

Scope of Work¶

1. OpenDental Data Retrieval

   • Retrieve data from OpenDental APIs
   • Use the existing DTO structures provided in the Google Drive link
   • Ensure data is mapped correctly into the OpenDental DTOs
   • Prepare the payload as per backend DTO

2. Sidexis Data Retrieval

   • Retrieve data from Sidexis
   • Create initial DTOs for Sidexis (can be refined later)
   • Focus on important fields only , specifically:
     • Image-related data (image id, type, path, capture date, etc.)
     • Patient mapping fields (patient id, external id, name)
   • DTO design should support future extension

3. Encryption

   • Before sending data, encrypt the payload
   • Encryption standard:
     • AES-256-GCM
   • Encryption should be applied consistently for:
     • OpenDental payload
     • Sidexis payload

4. Dummy Backend API for Validation

   • Create a dummy API endpoint (in a new project)
   • API should:
     • Accept the encrypted payload
     • Log or acknowledge receipt
     • Return a simple success response
   • No authorization required for this phase
   • Purpose is only to verify that the sync service works end-to-end

5. Configuration Awareness

   • Sync execution should respect:
     • Enable / Disable flag
     • Configured frequency
   • Configuration logic already implemented should be reused

Out of Scope¶

• Backend authorization
• Backend data persistence
• Full Sidexis DTO finalization
• Production-grade validation

Acceptance Criteria¶

• Data is successfully retrieved from OpenDental and mapped using provided DTOs
• Initial DTOs for Sidexis are created and populated with key fields
• Payload is encrypted using AES-256-GCM
• Encrypted payload is successfully sent to the dummy API
• Dummy API confirms receipt of payload
• Sync respects configuration rules (enable + frequency)