PCCP monitoring for AI-enabled medical devicesRecruiting design partners
Show, every month, that your cleared model is still inside its PCCP.
Truecourse Health checks the real-world performance of your deployed imaging AI against the bounds in your authorized Predetermined Change Control Plan, verifies each planned model update against your Modification Protocol before rollout, and drafts the record your QA team signs.
Built for RA/QA and ML leads at radiology, ophthalmology and pathology AI companies with one to five FDA clearances.
Sensitivity vs. PCCP lower boundIllustrative data
All sitesSite C, scanner vendor BPCCP lower bound 0.87
Month 15Subgroup below authorized bound, n = 412. Routed to RA/QA for a documented decision under the change protocol.
The problem
Postmarket obligations for AI devices are growing faster than the tools to meet them.
FDA is pulling postmarket performance monitoring into the premarket conversation, and asking industry how real-world AI performance should be measured at all. Most manufacturers are answering with spreadsheets.
~1,350
AI-enabled devices authorized by FDA as of early 2026, roughly double the 2022 count.
SpreadsheetsMetrics pulled by hand each quarter, with no link back to the bounds written into the PCCP.
MLOps dashboardsBuilt for engineers watching a model, not for a quality function that has to file a defensible record.
Manual QA reviewSenior RA/QA time spent assembling evidence instead of judging it, and subgroup gaps found late.
Where it fits
Your PCCP tells FDA what you will watch. Nothing yet watches it for you.
Truecourse Health sits downstream of the tools you already use to write the plan and run your quality system. It does not replace either.
Layer
What it covers
What it leaves open
PCCP authoring tools
Templates and content for writing a compliant change control plan.
Document generation. No monitoring of the deployed model.
AI observability platforms
Production model monitoring for MLOps teams and health systems.
Not tied to your authorized thresholds or to submission-ready output.
Academic drift research
Validated distribution-shift techniques for imaging models.
Published, not productized.
Truecourse Health
Real-world device data checked against your own PCCP bounds, planned updates verified against your Modification Protocol, and an audit-ready record handed to your eQMS.
Built on your PCCP
A PCCP makes three promises to FDA. Truecourse helps you keep them after clearance.
FDA's final guidance on PCCPs for AI-enabled device software functions splits every plan into three parts. Each one creates work once the device ships, and between updates the cleared model still has to stay inside its bounds.
Part 1
Description of Modifications
You committed to
The specific changes you may make without a new submission, such as retraining on new data or supporting a new scanner.
Truecourse
Shows which planned change real-world data is pointing toward, and flags early when the change you need falls outside the plan.
Part 2
Modification Protocol
You committed to
How each change is developed, validated and rolled out, with acceptance criteria set in advance.
Truecourse
Runs the candidate model in the background on real-world data from your sites and checks it against those criteria, overall and by subgroup, before anyone switches it on.
Part 3
Impact Assessment
You committed to
The benefits and risks of each change and how the risks are controlled.
Truecourse
Assembles the before-and-after evidence for each update into a signed record for your QMS.
The PCCP lifecycle Highlighted steps are where Truecourse does the work.
How it works
Your PCCP becomes the monitoring baseline.
We start from what FDA already authorized, not from generic anomaly detection.
Import your authorized PCCP
Metrics tracked, the modification protocol, and subgroup bounds go in as structured configuration.
Connect real-world data
Start narrow with DICOM metadata and FHIR observation feeds from deployment sites.
Watch drift and subgroups
Data and performance drift, using ground-truth-light methods from the published literature, stratified by site, scanner, device version and demographics. Undersized subgroups are flagged too.
Escalate to a person
An out-of-bounds signal routes to the action trigger your own change protocol defines. A human decides; the system records it.
Verify updates before rollout
When you retrain or extend the model under your PCCP, the candidate runs in the background on real-world data and is checked against your Modification Protocol's acceptance criteria, overall and by subgroup.
Generate the record
A postmarket surveillance report and, for each update, the Impact Assessment evidence, with e-signature and traceability, ready to file into the eQMS you already run.
Example PCCP configuration
# device: chest X-ray triage, K-number on filemetric: sensitivity
lower_bound: 0.87 # from authorized PCCPwindow: 30d rolling
subgroups:
- site
- scanner_vendor
- age_band
- sex
min_subgroup_n: 200
on_breach:
route_to: RA/QA lead
action: evaluate_under_ACP §4.2update_verification:
mode: shadow # per Modification Protocol
accept_if:
sensitivity: ">= 0.89"
max_subgroup_drop: 0.02
report:
cadence: monthly
signoff: required
Illustrative only. Field names and values are examples, not a product schema.
Who it's for
Lean imaging-AI teams without a dedicated MLOps group.
Class II AI/ML software as a medical device, roughly 20 to 300 people, with one to five devices cleared or close to clearance.
RadiologyOphthalmologyDigital pathology
For RA/QA leads
A recurring postmarket record mapped to what FDA's draft lifecycle guidance asks sponsors to describe.
Evidence tied directly to the bounds in your authorized PCCP.
Every escalation and decision captured with a signature trail.
For ML leads
Drift and subgroup performance views without building monitoring infrastructure in-house.
Thresholds set per device, not hardcoded defaults.
Early warning before a performance gap becomes a quality event.
Supplier qualification
Built to be qualified by your QA team.
FDA's final Computer Software Assurance guidance lets manufacturers lean on vendor evidence. We plan to hand you that evidence instead of making you build it.
Quality-system software, not a device.
Truecourse Health informs your decisions about your device. It never makes a clinical decision about a patient, and AI-drafted report text always goes through a human sign-off.
Documented development process with traceability and test evidenceFrom first commitThe core of a CSA vendor assessment.
Customer validation packBefore go-liveIntended use, risk rating per feature, test evidence and release notes, so your own validation work shrinks.
HIPAA business associate agreement and controlsBefore real dataDevice performance data can contain PHI.
SOC 2 Type I, then Type IIType I before paidThe standard ask on security questionnaires.
Part 11-style audit trail and e-signaturesIn the MVPEvery report traceable, and exportable into Ketryx, Greenlight Guru, Qualio or your own record.
Design partner program
We are working with three to five imaging-AI companies to shape the first version.
Truecourse Health is early. Before writing production code we are talking with RA/QA and ML leads about how they monitor deployed models today and what it costs them.
What design partners get
Discounted or free access through a full postmarket surveillance cycle.
Thresholds and report templates calibrated to your device and your PCCP.
Direct influence on what gets built first and how it fits your QMS.
What we ask
A 30-minute conversation about your current postmarket process. No pitch deck.
Candid feedback on early designs and sample reports.
If it fits, a pilot on one cleared device once security and BAA terms are in place.
Contact
Tell us how you monitor your deployed models today.
Leave your name and email and the founder will reply personally to set up a 30-minute conversation. Useful even if you never become a customer: you leave with a view of how peers are approaching PCCP monitoring.
How you track real-world performance and subgroups now