Regulatory Workflows and Interactions - pharma, published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/APIX---API-Exchange-for-Medicinal-Products/ and changes regularly. See the Directory of published versions
A consumer can follow a FedEx or Amazon package from βorderedβ to βdeliveredβ and get a notification at every step. RWI-pharma gives every party the same visibility into a regulatory interaction: each milestone is a Task status change, and each change is pushed to subscribers the moment it happens.
π¦ Package delivery
Order placed
β
Shipped
β
In transit
β
Out for delivery
β
Delivered
π Regulatory interaction
Submitted requested
β
Received received
β
Validated accepted
β
Under review in-progress
β
Decision completed
π·οΈ Tracking number
The Task and its groupIdentifier identify the interaction and every related Task in the procedure.
π Push notifications
A Subscription delivers each status change to the subscriberβs endpoint instantly β no portal log-ins, no polling.
π Delivery history
Every Task version is timestamped, so the full history can be replayed as a timeline or rolled up into dashboards.
Because every milestone is a timestamped, machine-readable event, the raw exchange data can be turned into decision-ready views with no manual data entry. Both examples below are built from the same underlying Task history.
Scenario Example 1 · Real-Time Status Tracking & Notifications
Single-Procedure Lifecycle Timeline (Shelf-Life Update Test Scenario)
This is the "FedEx tracking view" of one procedure at full fidelity. The timeline below is derived entirely from the timestamped Task versions of the shelf-life update test scenario (procedure NDA-214365-S-021): a terminally rejected first submission, filing review and user-fee clearance, two Information-Request clock stops (RTQ XML), and the closing approval. Hover over any bar or milestone to see the underlying Task ids and status transitions.
The same feed rolls up across the whole portfolio, giving an applicant a live pipeline view of every procedure at every agency:
Procedures by current phase · rolled up live from Task.status / Task.businessStatus across every connected regulator · hover a segment for detail
Scenario Example 2 · Regulator Performance Dashboards
From the Same Data: Live Operations Board and Statutory Performance Reports
Regulators get the mirror image of the applicant's tracking view — for free. Because every procedure is an RWI-pharma Task with a full, timestamped status history, an agency can generate performance dashboards directly from its own exchange data: a real-time board of current activity, and aggregated quarterly or annual performance reports.
A — Live Activity Board (Flight-Board View)
A real-time view of everything currently in the house — like an airport departure board. Each status change anywhere in the agency updates the board instantly via the same subscription framework offered to applicants.
ACTIVE PROCEDURES — LIVE
auto-refreshed by subscription notifications · last event 14:32:07 UTC
PROCEDURE
PRODUCT
TYPE
CURRENT PHASE
DAY
STATUS
SUB-2027-1204
Dermacort 1% cream
Type IA Variation
Submission received
0
● RECEIVED
VAR-IB-2027-118
Cardizal 5 mg
Type IB Variation
Technical validation
2
● VALIDATION
MAA-2027-0057
Virestat 200 mg
Initial MAA
Filing review
12
● IN REVIEW
MAA-2027-0042
Oncomab 50 mg
Initial MAA
CMC assessment
142
● IN REVIEW
NDA-214365-S-021
Stelbatolol 10 mg
Supplement (shelf-life)
Awaiting applicant response (IR 001)
133
❚❚ CLOCK STOP
REN-2027-031
Neurofen XR 75 mg
Renewal
Decision preparation
55
◆ DECISION DUE
VAR-II-2026-889
Oncomab 50 mg
Type II Variation
Closed
201
✓ APPROVED
Every row is a parent RWI-pharma Task; the CURRENT PHASE column is Task.businessStatus and the STATUS column is Task.status. A task-update subscription notification flips the row the moment an assessor changes the Task — no polling, no data entry. Note the shelf-life test scenario (NDA-214365-S-021) sitting in its first clock stop, exactly as shown on the timeline in Scenario Example 1.
B — Quarterly & Annual Performance Reports
The same event history, aggregated over a reporting period, produces the statutory performance metrics that agencies publish today through manual compilation — outcome counts, average review times by procedure type, and bottleneck analysis. With RWI-pharma these are a query, not a project.
Median time to approval — the headline figure of a regulator’s annual performance report (e.g., a PDUFA-style report to Congress or an EMA annual report), computed directly from Task timestamps instead of manual compilation:
Median Time to Application Approval (Months)
PriorityStandard
8.0
12.0
2021
7.9
11.5
2022
7.8
13.0
2023
7.7
12.2
2024
7.9
10.9
2025
Fiscal Year of Approval · computed from Task.authoredOn → Task.lastModified (approved)
First-cycle approval rate — the quality-of-review metric regulators publish each year, derived from the Task status history (was the application approved without a resubmission cycle?):
Percent of Applications Approved on the First Cycle
PriorityStandard
Fiscal Year of Application Receipt · first-cycle = approved without a resubmission cycle · hover a point for the value
Bottleneck detection — where does the time actually go?
Average Days per Phase
Regulator clockApplicant clock
Average across procedures closed in the last 12 months · days · clock-stop time is applicant time, not regulator time
βΉοΈNote: For a step-by-step technical walkthrough of this use case, visit the Workflow page.