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

Include Stamped OID in BundleDigest Info #17092

Open
3 tasks
arnejduranovic opened this issue Jan 17, 2025 · 1 comment
Open
3 tasks

Include Stamped OID in BundleDigest Info #17092

arnejduranovic opened this issue Jan 17, 2025 · 1 comment
Assignees
Labels
platform Platform Team

Comments

@arnejduranovic
Copy link
Collaborator

arnejduranovic commented Jan 17, 2025

User Story

As a ReportStream Engagement engineer,
I want to see the OID values associated with conditions,
so that I can quickly evaluate if a particular filter should have passed or failed.

Description/Use Case

#14511 Stamped a test's OID alongside its associated condition. We want to make this available in azure events.

Risks/Impacts/Considerations

Our events are getting large and violate the ~8000 character limit of an azure event property. We should try to minimize the size increase this ticket necessitates.

Dev Notes

Acceptance Criteria

  • Update FhirPathBundleDigestLabResultExtractorStrategy to include OID info
  • @jsutantio notified of changes to event structure so that Dashboard can be updated
    • @jsutantio must be notified of exact time this is deployed to staging and production so that she knows the cut-off for updating the dashboard
@arnejduranovic arnejduranovic added platform Platform Team ready-for-refinement Ticket is a point where we can productively discuss it labels Jan 17, 2025
@MichaelEsuruoso
Copy link
Collaborator

@jsutantio jsutantio removed the ready-for-refinement Ticket is a point where we can productively discuss it label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Platform Team
Projects
None yet
Development

No branches or pull requests

4 participants