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

[SPIKE] Identify why custom FHIR Path functions are not always recognized #16863

Open
3 tasks
chris-kuryak opened this issue Dec 20, 2024 · 0 comments
Open
3 tasks
Labels
engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.

Comments

@chris-kuryak
Copy link
Collaborator

Problem statement

A rare exception occurs in ReportStream where custom FHIR Path functions are not recognized the the message errors our. But upon resubmission, they are recognized and the message processes successfully.

What you need to know

Acceptance criteria

  • Issue is identified and potential solutions developed
  • Solution aligned between Engagement Tech Lead, Platform Tech Lead, and Systems Architect
  • Follow-on ticket(s) to implement solution is created and linked to this ticket
@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.
Projects
None yet
Development

No branches or pull requests

1 participant