A real-time PMA supplement is a narrow regulatory vehicle. Section 737(4)(D) of the Federal Food, Drug, and Cosmetic Act defines it as a supplement requesting a minor device change, such as a minor design, software, sterilization, or labeling change, where the applicant has requested and FDA has granted a meeting or similar forum to jointly review and determine the supplement's status [1]. Researching these records therefore starts with a definitional filter, not a keyword hunt. The public FDA databases treat "Real Time Process" as a discrete supplement type value, but the underlying records rarely explain why a specific change qualified for real-time review or what was discussed at the joint meeting. A disciplined workflow must separate statutory text from guidance recommendations, and database fields from submission content. The value of the research lies in documenting what can and cannot be established about a specific supplement from public sources.
Anchoring the Statutory and Regulatory Boundary
Real-time supplement records begin with two legal documents: the Act's definition and 21 CFR 814.39. The statutory definition in section 737(4)(D), as incorporated into the December 2008 modifications guidance, specifies a supplement requesting a minor change for which the applicant requested and FDA granted a meeting or similar forum to jointly review and determine status [7]. The regulation itself does not create a separate substantive test for real-time supplements; it establishes the general obligation to submit a PMA supplement before making any change affecting safety or effectiveness, unless FDA has advised an alternate submission or the change falls under section 515(d)(6)(A) [4]. Understanding this hierarchy matters because a database entry labeled as a real-time supplement reflects an accepted submission type, not a regulatory conclusion that the change was minor.
The December 2019 real-time supplement guidance narrows the practical scope. FDA states it believes a real-time PMA supplement is appropriate for a minor change expected within a product line, including changes to device design, software, instructions for use, warnings, precautions, or labeling that does not affect indications or contraindications, and sterilization and packaging methods [2]. The guidance also says a minor change should be expected for that device type and validated according to scientific principles relied on in previous reviews and accepted test methods [2]. A manufacturer's own characterization of a change as minor therefore cannot be taken from the database alone. The public record does not show whether those validation expectations were met.
Mapping the Record Layers That Contain Real-Time Data
The FDA Premarket Approval database exposes real-time supplements through a filterable field. The database search interface includes a "Supplement Type" selector with a "Real Time Process" option [5]. That selector allows a researcher to constrain results to submissions FDA classified under that value. The openFDA device PMA reference documentation lists supplement_number and supplement_type as indexed fields, with supplement_type linked to 21 CFR Part 814 and serving as an exact indexed field [6]. This means a researcher can query for real-time supplements as a coded category rather than inferring the category from free text. The trade name, applicant, decision date, and date received fields are also available [6].
The limitation is that the database record is a submission envelope. It identifies the PMA number, supplement number, submission type, applicant, and decision date, but it does not contain the supplement's cover letter, the joint meeting minutes, or the review memo explaining why a change was considered minor. The real-time guidance describes a four-step request process: a preliminary discussion with the appropriate CDRH review division or CBER applications division, a written request, FDA's response, and a determination of interaction type [2]. None of those steps are systematically exposed as structured fields. Researchers who treat the database as the endpoint will miss the fact that the actual regulatory rationale sits in documents that may never be public.
A Minimal Research Note Format for Real-Time Supplements
A reproducible note should contain seven fields: PMA number, supplement number, applicant, trade name, decision date, date received, and supplement type as retrieved from the FDA PMA database [5][6]. Add a status line noting whether the record shows a real-time process classification but does not include the meeting request, FDA response, or joint review determination because those are not exposed in the structured dataset [2]. Then state the claim limits: the database entry supports only that a real-time-classified supplement decision exists, not that the underlying change was minor, expected for the device type, or validated by accepted test methods [2].
For a longitudinal check, record whether the supplement appears under the same PMA number as an original or panel-track supplement and note that the 21 CFR 814.39 framework requires supplements before safety-or-effectiveness-affecting changes, with the burden primarily on the PMA holder [3][4]. Do not infer from a later periodic report that the change was reported instead of supplemented unless the correspondence is available showing FDA's alternate submission advice [4]. When a new indication appears, mark it as outside the real-time examples discussed in the 2008 guidance, where FDA stated it was not aware of an appropriate real-time situation for indication changes [7]. This format keeps the research claim aligned with the actual record.
A Suggested Workflow for Evaluating a Specific Real-Time Record
As a suggested demonstration, suppose a researcher needs to evaluate a real-time supplement for a Class III device change. Step one is to retrieve the record in the FDA PMA database using the PMA number and confirm the supplement_type value is the real-time process [5]. Step two is to record the applicant name, supplement number, decision date, and date received, all of which are exposed fields [6]. Step three is to compare the stated change category, if disclosed elsewhere, against the criteria in the real-time guidance: device design, software, labeling that does not affect indications or contraindications, or sterilization and packaging [2]. A change to a new indication would not fit that scope, and the 2008 decision-making guidance states FDA is not aware of a situation in which a real-time supplement would be appropriate for changes affecting an indication for use [7].
Step four is a negative check for unrecorded facts. The public database will not show whether FDA and the PMA holder agreed before submission that the review could be achieved in a real-time setting, a condition the guidance identifies for an effective route [2]. It will not show whether the change was supported by preclinical or animal testing with no new clinical data, a characteristic described in the FDA postapproval presentation [8]. It will not show the single scientific discipline involved in review or the 90-day review figure that appears in FDA's summary table [8]. These are properties of the underlying submission and review, not the database row. A research note should state that the record confirms submission type and decision but does not evidence the full real-time eligibility rationale.
Evidence Limits and Decision Points in the Public Record
Decision points in this research are mostly about absence. The PMA database includes a real-time supplement type value, but the openFDA field documentation describes supplement_type generally, not a definition of the real-time process value itself [6]. The database's "Page Last Updated" notation indicates currency of the tool, not completeness of every historical submission [5]. A researcher therefore cannot assert from a single database hit that the supplement met the statutory minor-change definition. The strongest defensible statement is that the submission was accepted and processed under the real-time supplement category according to FDA's retrieval system.
The guidance documents are nonbinding, and that constraint applies to the research interpretation. The real-time guidance states explicitly that FDA guidances describe current thinking and should be viewed only as recommendations unless specific regulatory or statutory requirements are cited [2]. The use of "should" indicates suggested, not required, action [2]. When a researcher says a real-time supplement should involve only minor changes, that is a recommendation from guidance, not a legal finding under 21 CFR 814.39. When the law applies, the controlling language is the section 737(4)(D) definition, which requires the joint review arrangement [1]. Keeping those two registers separate prevents a researcher from converting nonbinding expectations into statutory claims.
Sources & references
- PMA Supplements and Amendments | FDA · www.fda.gov
- Real-Time Premarket Approval Application (PMA) Supplements - Guidance for Industry and FDA Staff · www.fda.gov
- eCFR :: 21 CFR 814.39 -- PMA supplements. · www.ecfr.gov
- 21 CFR § 814.39 PMA supplements. · www.ecfr.gov
- Premarket Approval (PMA) - accessdata.fda.gov · www.accessdata.fda.gov
- Section Field Name Type Description This equates to the review division within CDRH in which the PMA would be reviewed, · open.fda.gov
- Modifications to Devices Subject to Premarket Approval (PMA) - The PMA Supplement Decision-Making Process — December 11, 2008 · www.fda.gov
- Premarket Approval Application (PMA) Program: Postapproval Requirements — FDA PowerPoint · www.fda.gov