Middle Tier to Triage the file transfer for Image Module
Posted: Fri Oct 17, 2025 11:57 am
Few questions, thoughts and suggestions on this.
Currently we need https services and SMPT services to connect to OD. Of course there are other combinations also there. I understand the original architecture to separate database access from file access. I believe the separation helps network / SMPTP / Dropbox to handle the file transfer between the file server / Network drive (and workstation) without bogging down the database traffic between the workstation and server. This solution is well intended for a single office with server in the office setup.
Now OD has entered the era of API, the middle tier / API Services is equipped with capability to triage the file transfer (related to image module). I believe this is a step in the right direction. As it could encapsulate the file location from the 3rd party. I believe currently the API post is expected to provide SMTP details including credentials to triage the file transfer (for image module). If the middle tier holds the SMTP / Network drive / drop box credentials the middle tier can handle the file transfers without API to provide the details. This will also help avoid the dental office share the SMTP details with the vendor.
If the middle tier (API services) is able to handle file transfers for workstation, we don't need to worry about workstation having to have access to network / local drive.
I believe in my opinion this reduces the architectural complexity in deploying OD for clients with multiple locations.
I welcome additional thoughts on this.
Currently we need https services and SMPT services to connect to OD. Of course there are other combinations also there. I understand the original architecture to separate database access from file access. I believe the separation helps network / SMPTP / Dropbox to handle the file transfer between the file server / Network drive (and workstation) without bogging down the database traffic between the workstation and server. This solution is well intended for a single office with server in the office setup.
Now OD has entered the era of API, the middle tier / API Services is equipped with capability to triage the file transfer (related to image module). I believe this is a step in the right direction. As it could encapsulate the file location from the 3rd party. I believe currently the API post is expected to provide SMTP details including credentials to triage the file transfer (for image module). If the middle tier holds the SMTP / Network drive / drop box credentials the middle tier can handle the file transfers without API to provide the details. This will also help avoid the dental office share the SMTP details with the vendor.
If the middle tier (API services) is able to handle file transfers for workstation, we don't need to worry about workstation having to have access to network / local drive.
I believe in my opinion this reduces the architectural complexity in deploying OD for clients with multiple locations.
I welcome additional thoughts on this.