It is possible for the tracking ID to be longer than the column limit when observations get filtered out

[mkalish]

User Story

As a report stream dev, I would not like to have column limits cause an exception in PROD.

Description/Use Case

The tracking_id column in the action_log table is configured to have a max length of 128 characters; this is currently acceptable when processing FHIR sent by simple report, but in reality it is quite easy to exceed.

For example (generated from an SR message) 3ad338c6-125d-4141-9ce1-6040481304ab at 623a1a02-6925-3595-affd-271175822707 with http://loinc.org code: 95421-4 is 112 characters

Risks/Impacts/Considerations

Dev Notes

Long term, it makes sense to drop the length limitation on the column just for safety, but since the current values do not make sense as a tracking id anyway that can be deferred to a follow up ticket.

Code

Acceptance Criteria

• [ ] The tracking_id for the action log when an observation is filtered is just bundle.identifier.value and the longer string is move into the message
• [ ] A follow up ticket is created to remove the length limit on the column