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

Pacman: Message Parsing Service #439

Open
1 task
emmastephenson opened this issue Feb 28, 2025 · 0 comments
Open
1 task

Pacman: Message Parsing Service #439

emmastephenson opened this issue Feb 28, 2025 · 0 comments
Labels
streamline eCR Issues for the Streamline eCR team tech debt Technical debt related issue

Comments

@emmastephenson
Copy link
Collaborator

What needs to be done

Move message parsing functionality that's used by the eCR Viewer directly into the orchestration service.

Why it needs to be done

This will make our application stack significantly easier to maintain, and should also improve our networking performance for the Viewer.

Acceptance Criteria

  • eCR Viewer pipeline doesn't call out to message parser to extract data - it's done directly in orchestration.

Technical Notes

Notes from planning epic:

  • Extracting fields out of the FHIR bundle in a flattened way
  • May not want to port over PHDC conversion pieces
  • Less about moving over existing codebase, and more about extracting the data out directly. What gets returned to eCR Viewer as metadata

Additional context

Full epic context here

@emmastephenson emmastephenson added streamline eCR Issues for the Streamline eCR team tech debt Technical debt related issue labels Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
streamline eCR Issues for the Streamline eCR team tech debt Technical debt related issue
Projects
None yet
Development

No branches or pull requests

1 participant