You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Issue
FhirEngine package is reponsible for handling all apis related to storage.
Sync package is reponsible for handling all apis related to sync.
However we identified certain issues in the current implementation of placing the sync APIs in the FhirEngine interface:-
Tightly coupled Sync and FhirEngine packages.
Misplaced responsibilities like UploadProgress in FhirEngine package
Redundant data models like SyncUploadProgress and SyncJobStatus.InProgress
We realized that these issues stem from the assumption that the custom sync APIs (syncUpload and syncDownload) are used against a FHIR-server. This makes using the sync APIs in the FhirEngine interface difficult.
Hence we decided to refactor the sync APIs and move them to an internal interface just like FhirEngine called FhirSyncDbInteractor.
More information in this doc.
Would you like to work on the issue?
The text was updated successfully, but these errors were encountered:
MJ1998
changed the title
FhirSyncDbInteractor: move FhirEngine's sync APIs to an internal abstract db layer.
FhirSyncDbInteractor: move FhirEngine's sync APIs to an internal DB wrapper interface
Mar 4, 2024
MJ1998
changed the title
FhirSyncDbInteractor: move FhirEngine's sync APIs to an internal DB wrapper interface
Decoupling Sync APIs from FhirEngine for Broader Functionality
Mar 4, 2024
Describe the Issue
FhirEngine package is reponsible for handling all apis related to storage.
Sync package is reponsible for handling all apis related to sync.
However we identified certain issues in the current implementation of placing the sync APIs in the FhirEngine interface:-
We realized that these issues stem from the assumption that the custom sync APIs (syncUpload and syncDownload) are used against a FHIR-server. This makes using the sync APIs in the FhirEngine interface difficult.
Hence we decided to refactor the sync APIs and move them to an internal interface just like FhirEngine called FhirSyncDbInteractor.
More information in this doc.
Would you like to work on the issue?
The text was updated successfully, but these errors were encountered: