Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use NATS for CoreWorkflow transmit step #296

Open
ccorley opened this issue Oct 19, 2021 · 0 comments
Open

Use NATS for CoreWorkflow transmit step #296

ccorley opened this issue Oct 19, 2021 · 0 comments
Assignees
@ccorley

Comments

@ccorley
Copy link

ccorley commented Oct 19, 2021 •
edited
Loading

Investigate moving the transmit implementation out of CoreWorkflow (the transmit step would still remain in CoreWorkflow). Create a NATS subscriber that handles transmission of messages to defined transmit servers (right now FHIR servers) and returns the response via a) another NATS message or b) a callback.

Consider moving transmission settings to a .yaml file and make the settings more general.
@ccorley ccorley self-assigned this Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ccorley ccorley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ccorley