samply
/
bridgehead
mirror of https://github.com/samply/bridgehead.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Got rid of project specific stuff

This commit is contained in:
DavidCroftDKFZ 2025-04-04 13:28:34 +02:00
parent 8e114f096a
commit 87e54f552e
1 changed files with 1 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -444,19 +444,11 @@ See the first question for the control mechanism.
</details> </details>
<details> <details>
<summary><strong>Q: Is data only transferred one-way (Bridgehead/FHIR Store → GBN Node), or is two-way access necessary?</strong></summary> <summary><strong>Q: Is data only transferred one-way (Bridgehead/FHIR Store → Central/Locator), or is two-way access necessary?</strong></summary>
A: By using Samply.Beam, only one outgoing connection to the broker is required at the network level (i.e., Bridgehead → Broker). A: By using Samply.Beam, only one outgoing connection to the broker is required at the network level (i.e., Bridgehead → Broker).
</details> </details>
<details>
<summary><strong>Q: Are there already thoughts regarding data export from Centraxx to Bridgehead/DZPG Node?</strong></summary>
A: TransFAIR would be a good option for loading the data from the DIZ into the BK.
CentraXX has the FHIR export interface, which is expensive.
Our colleagues in Frankfurt and Mainz have already developed a data integration tool for CentraXX export—perhaps we could exchange ideas here.
</details>
## Troubleshooting ## Troubleshooting
### Docker Daemon Proxy Configuration ### Docker Daemon Proxy Configuration