Obtain the current Reportable Conditions Trigger Codes (RCTC) value sets from the relevant authority (verify the current source and release cycle in the eCR FHIR IG or from the CDC eCR program); these value sets contain codes for diagnoses, lab results, medications, and other clinical events that should trigger an eICR.
Implement terminology matching logic in the clinical system or middleware that compares codes on new or updated clinical events (diagnoses, lab orders/results, medications) against the RCTC value sets.
When a triggering code is detected, initiate the eICR creation process by collecting the required clinical data sections and assembling the eICR Composition Bundle.
Consider the timing rules in the eCR IG — an eICR may need to be sent at specific points in the encounter lifecycle (e.g., at encounter close or when a lab result is resulted); verify the triggering timing requirements.
Update the trigger code matching logic whenever a new RCTC release is published; the value sets are updated periodically as new reportable conditions are added.
Log trigger events for audit purposes, recording which code triggered the report and at what time.
Known gotchas
RCTC value sets are updated on a scheduled release cycle — a static snapshot will become outdated and may miss newly added reportable conditions or retain removed codes.
Trigger code matching should use the code system and code together, not the display text, to avoid false positives or misses due to synonym variation.
Not every trigger necessarily results in a reportable condition — the public health agency's RR will confirm reportability; the trigger initiates the report but does not determine outcome.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp