RCM : Reg Alert vs Source Document
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2025 06:06 AM
If a customer says that at the end an alert will be a part of a source document, why do I need two different types of alerts, (Reg Alert vs Source Document) what should one say?
And why do we need a source document table for import, we can directly add new citations in citations table?
Is it just to manage approvals through import tasks?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2025 06:06 AM - edited 06-09-2025 06:07 AM
Anyone please help with this once you are free
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2025 06:09 AM
@ANOOP_CHERIAN tagging you for your reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2025 06:17 AM
A Regulatory Alert is a notification that informs compliance professionals when there’s a change in the regulations or laws that a business or firm must follow.
Example:
Imagine that a new privacy law is passed in your country, and your company needs to update its data security practices to stay compliant. A Regulatory Alert issued by the regulator would notify you immediately about the new law, explaining the changes and telling you what needs to be done to ensure your company complies. This alert might also provide a deadline for when the changes need to be implemented.
A Source Document on the other hand, is any type of official document or rulebook that provides important information regarding laws, regulations, and guidelines. Depending on the content integration needs, these are generated by the respective regulatory intelligence data providers.
Example:
If a business in the EU or one that does business with EU citizens receives a Regulatory Alert about an update to GDPR, the system will likely link directly to the GDPR Source Document to help users read and understand the changes.
Customer's scenario:
- An agency update is published for a proposed/final rule change to "BOX Rule 2000". This change is sent to the business as a regulatory change event of type = "Regulatory Change Event"
- A rulebook (Authority Document) is updated and there is a change to the contents of a citation. E.g. "BOX Rule 2000". This change is sent to the business as a regulatory change event with type = "Source Document"; specifically stating one of the citation has undergone change. The import document task flow acts like an action plan for record keeping purpose in the system of records so that the citation record prior to insertion either as Insert or Update is managed with appropriate due diligence measures i.e. ownership accountability and traced back with the regulatory alert that influenced the implementation activity.