The founder problem
Regulatory updates often arrive as long documents, webinars, notices, guidance pages, or inspection-program changes. The founder question is much simpler: does this affect our product, our next submission conversation, our quality records, or what we can say to customers and investors?
The hard part is not only summarizing the document. The hard part is linking the change to one product, one claim boundary, one evidence plan, and one reviewer-owned action path.
What a Product ID impact map should show
- Which Product ID, product family, or variant is in scope.
- Which jurisdiction and source triggered the review.
- Which candidate regulatory lenses may be affected.
- Which claims, labels, risk controls, test plans, SOPs, QMS records, or postmarket processes may need review.
- Which facts are public, customer-confirmed, assumed, or unknown.
- Which questions need RA/QA, consultant, legal, clinical, or management review.
What the SOP packet should contain
A useful SOP packet should not simply say 'update the SOP.' It should show the source, the product link, the old workflow area, the possible new workflow area, the reviewer question, and the destination for the approved decision.
| Layer | Reviewer-ready output |
|---|---|
| Source | Official URL, date, summary, scope, and limitations. |
| Product fit | Product ID, claim boundary, candidate regulatory lenses, and affected workflow. |
| Review point | What RA/QA or consultant should accept, reject, clarify, or assign. |
| Decision record | Approved action, rationale, owner, destination, and next review trigger. |
Where the workspace helps
In the workspace, the user should be able to open the Product ID, paste or select the regulatory signal, see the affected evidence map, and generate a reviewer packet. The output should be a draft review workflow, not an auto-approved procedure.
That is the useful demo: a founder brings a regulatory signal, the workspace turns it into a product-specific review packet, and RA/QA approves or changes the action before anything becomes an SOP update.
What TrueMedDevice can prepare
TrueMedDevice can prepare a regulatory-change impact review, SOP update candidate map, source ledger, affected-record checklist, open reviewer questions, and decision-memory record for one Product ID.
Source ledger
What it can tell you
FDA's current QMSR page, including effective-date context, inspection-program references, and quality system resources.
What it cannot decide
Whether a specific manufacturer, product, procedure, supplier file, audit record, or SOP has reached any compliance status.
What it can tell you
Current and historical FDA guidance documents that may affect device submissions, labeling, testing, quality records, or postmarket work.
What it cannot decide
Which guidance is controlling for your exact product, indication, jurisdiction, or evidence plan.
What it can tell you
Public database families for 510(k), Premarket Approval (PMA), De Novo, Product Classification, Total Product Life Cycle (TPLC), recalls, and other device records.
What it cannot decide
Whether public records are complete enough to determine your route, obligations, or next quality-system action.
What it can tell you
Canadian public recall and safety-alert records that can trigger a regulatory-change or postmarket review question.
What it cannot decide
Whether a Canadian change requires a specific internal procedure, licence action, label change, or field action.
Frequently asked questions
Can TrueMedDevice tell us whether a new rule applies to our product?
We can map why a rule, guidance, or notice may be relevant and what facts need review. We do not make the final applicability, compliance, legal, or approval decision.
Is this only for the FDA?
No. The same Product ID workflow can organize United States Food and Drug Administration (FDA), Health Canada, or other public regulator signals, as long as the source, jurisdiction, and limitations are preserved.
What does the RA/QA reviewer receive?
A source-backed review packet with affected product facts, candidate workflow impacts, SOP sections to review, open questions, and a decision-record template.
Does the system rewrite our SOP automatically?
No. It can draft candidate update language and review points, but a qualified owner must review, approve, route, and implement any SOP change through the company's own QMS.
Need a rule-change review around one Product ID?
Send the product family and the regulatory signal you are trying to understand. We can scope a first source-backed impact packet for qualified review.