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.

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

Update Orchestration Service so it can use the eCR Viewers save-metadata Endpoint #2502

Closed
2 tasks
JNygaard-Skylight opened this issue Sep 6, 2024 · 0 comments · Fixed by #2554
Closed
2 tasks
Assignees
Labels
Streamline eCR Issues for Streamline eCR team to work on

Comments

@JNygaard-Skylight
Copy link
Collaborator

JNygaard-Skylight commented Sep 6, 2024

What needs to be done

Add the eCR Viewer's new save-metadata endpoint to the Orchestration service, so that it can be used as a workflow step.

Why it needs to be done

Once this has been implemented we can remove the manual SQL calls in the seed-data script to insert metadata, and use just the Orchestration service (#2368). In addition this will enable the ability to pass the output of the message-parse to the save-metadata endpoint (#2368).

Acceptance Criteria

  • Update /api/save-fhir-data in Orchestration service to handle the optional metadata paramter
  • As part of a Orchestration config you should be able to save an eCRs metadata.

Technical Notes

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Streamline eCR Issues for Streamline eCR team to work on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant