Policy Pulse — User Guide

1. What Policy Pulse does

Policy Pulse is a Confluence global app that monitors regulatory standards, living guidelines, and agency news — then surfaces what matters on one dashboard and on individual pages.

• Standards watchlist: traffic-light view of versioned standards with current and upcoming revisions.
• Living guidelines: publisher URL monitoring for documents without fixed edition numbers.
• Regulatory news: RSS feeds from FDA, EMA, EU, ISO, UK ICO, and other configured sources.
• AI summaries: on-demand news impact summaries and automatic revision enrichment.
• Page byline: alert counts on Confluence pages linked to relevant standards.
• Workflow: acknowledge alerts and create Jira SOP tasks when configured.

2. Opening Policy Pulse

1. In Confluence, open the app launcher or Apps.
2. Select Policy Pulse.
3. Review the metric strip and choose a tab: Standards, Living guidelines, or News.

3. Standards tab

Use filters for search, agency, sector, and period. Standards are grouped by risk (red / amber / green).

• View opens the detail panel with current edition and upcoming updates.
• Jira column shows open tasks; Jira review at the bottom of the panel creates one SOP task per standard.
• Acknowledge appears on upcoming revisions when your team has reviewed a change.

4. Living guidelines tab

Guidelines tracked by publisher URL (e.g. GAMP, certain NIST publications). Same table layout and filters as Standards.

5. News tab

Regulatory news from enabled RSS feeds. Filter by agency, period, and risk level.

• Summarize — AI impact summary with recommended actions.
• Acknowledge — mark as reviewed.
• Jira — expands a Jira review panel to create or track tasks.

Feeds refresh hourly. Poll now appears only when your administrator enables manual polling.

6. Page byline alerts

On Confluence pages, a compact Regulatory alerts byline shows high-priority standard updates and relevant news when the page matches your watchlist (by title or admin page mapping). Open Policy Pulse for full detail — the byline shows counts, not full change text.

7. A day in the life

This walkthrough follows a realistic scenario: FDA’s transition away from 21 CFR Part 820 (QSR) and how a quality team uses Policy Pulse across the dashboard, Confluence SOP pages, and Jira. It assumes your administrator has enabled 21 CFR Part 820 on the watchlist, set a Jira project key (e.g. QMS), and mapped your QMS SOP Confluence page to that standard.

How detail flows

Surface	What you see	How it updates
Policy Pulse app	Full editions, news, Jira task table	Live when you load or refresh
Confluence byline	Counts only (mapped standards, updates, notices)	When the page loads
Alert index (optional)	HTML table of open news and at-risk standards	When an admin publishes the index
Jira issues	Rich description at task creation	Snapshot at create — edit in Jira if needed
Jira status in Policy Pulse	Status, assignee, dates	When you click Refresh in Jira review

Phase 0 — Administrator setup (one time)

1. Open Confluence → Settings → Policy Pulse.
2. Enable FDA / 21 CFR Part 820 on the watchlist.
3. Set Jira project key (e.g. QMS).
4. Under Page mappings, link QMS SOP — 21 CFR Part 820 to the standard.
5. Optionally publish the alert index page in your alert space.

Phase 1 — Quality specialist reviews the standard

Maria, QA lead

1. Open Apps → Policy Pulse → Standards.
2. Find 21 CFR Part 820 and click View.
3. Read current and upcoming editions in the detail panel.
4. In Jira review, click Create Jira task (e.g. QMS-142).
5. Verify the Jira description includes edition dates, summaries, and source links.

Phase 2 — Regulatory affairs triages news

James, regulatory affairs

1. On News, filter FDA or search QMSR / 820.
2. Click Summarize, then Jira → Create Jira task (e.g. QMS-143).
3. Click Acknowledge when the team has reviewed the item.

Phase 3 — SOP author on the Confluence page

Priya, document owner

1. Open the mapped page QMS SOP — 21 CFR Part 820.
2. Check the Regulatory alerts byline for mapped-standard and notice counts.
3. Open Policy Pulse for full detail and confirm QMS-142 is still open.

Phase 4 — Close the loop in Jira

Alex, assignee

1. Complete the assessment and move QMS-142 to Done in Jira.
2. In Policy Pulse → Jira review → Refresh — task moves to Task history.
3. Acknowledge the revision when the dashboard item is handled.

8. Limitations and tips

• Watchlist: you only see agencies and standards enabled by your administrator.
• AI: summaries and scanner results are assistive — verify against official sources.
• Jira: requires Policy Pulse on Jira and a configured project key.

9. Troubleshooting

• Empty dashboard: check watchlist with your administrator.
• Summarize fails: retry; ask admin about Forge LLM availability.
• Jira fails: confirm project key and Jira install.
• No byline alerts: page may not match any standard — ask about page mappings.

10. Support

Need additional standards, regulatory feeds, or news monitoring threads? Contact us via App support (from your site's Connected apps listing for Policy Pulse) or email support@helmlabs.uk.