-
Notifications
You must be signed in to change notification settings - Fork 20
FHIR Bridge code refactoring proposals/ideas #442
Comments
In addition:
|
|
|
@subigre pls no google coding style, i would prefer the one we have currrently (at least for the tabulators), or do you have any other preferences ? |
¨WARNING: An illegal reflective access operation has occurred |
What is with the JUNIT test that tests coding codes (terminology server), i think we can delete those. |
|
Add exception catcher for timeconverter, since the bride does not show if an error occurs |
provide script to autoupdate opts and profiles via just entering the urls |
Converters used in conversion API should always:
|
Background
The current FHIR Bridge codebase is becoming bigger and it is sometimes hard to organize/find/maintain the code.
In addition, we use a lot of third-party librairies and the dependency management is becoming very hard.
The following non-exhaustive list contains some ideas/proposals for the next code refactoring in order to improve the development, testing and maintenance.
Maven multi-module project
The project structure should be re-think in order to organize the codebase using different modules:
fhir-bridge-camel
fhir-bridge-fhir
fhir-bridge-app
fhir-bridge-openehr
fhir-bridge-converters
fhir-bridge-core
fhir-bridge-utils
Define custom transactions
We should think about defining a list of transactions like IHE is doing: ITI-65, ITI-68, etc.
This could also help to:
The text was updated successfully, but these errors were encountered: