Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Triggering new event codes

Updated on April 26, 2021

New event codes can be easily implemented in the SCE utilizing a standard function during development. To add an event code to the claim, the function CE_SetEventCode is utilized. The parameters for this are the event code ID, a check to indicate a line number is being passed and then the claim line number. Once added, the event code can be seen in the clipboard in the pyWorkPage.EventListOpen structure if the claim is pended or the pyWorkPage.EventList if the claim is approved or resolved.

An example of assigning an event code through a collection is below:

Selecting the event code function from the list will present the fields for the appropriate variables to be added in the collection step:

The assignment of an event code to the claim performs validations in the system. The following table details the errors and where appropriate, the event codes, that are applied if the assignment fails.

ScenarioError Message
Event code configuration is not found in the system - sets event code: SGB-0046Event not found
Event code configuration is inactiveEvent inactive
Event code header data is not matched (for example: dates of service, claim type, claim identifier)Event header data inapplicable
Event code disposition is not found (for example: adjudication date, claim type, claim identifier, submission type, media type) – sets event code: SGB-0047Disposition not found
Event code disposition action is set to ignoreIgnore disposition
Event code is already raisedDuplicate event
Event code is overriddenOverride event
Event code is reported on denied claim lineEvent raised on denied line
On any logical errorError

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us