1.1.1 - Medical Device Status and Software Exclusions
0% read
Medical device status and software exclusions
FDA Device Status and Pathways / Jurisdiction and Device Classification
FoundationalCurrent-state reference: November 1, 2026Estimated time: 20-25 minutes
A defensible premarket strategy starts with a narrower question than which submission to file: what does each product function do, and does that function meet the statutory device definition after applicable software exclusions are considered?
What you will learn
Device status and jurisdiction: apply the intended-purpose and mechanism elements of section 201(h)(1) to a product description.
Software exclusions: distinguish administrative and record-management functions from functions requiring further device-status analysis under section 520(o).
Clinical decision support: evaluate whether a clinician can independently review the basis for recommendations rather than rely primarily on the output.
Regulatory documentation: prepare a function-specific assessment with supporting facts, a bounded conclusion, and unresolved questions.
Blueprint mapping
FDA device status and pathways → medical device definition and software exclusions → objectives bp.d1.t1 and bp.d1.t2. Topic weight is not supplied.
Prerequisites
None.
Key outputs
a function inventory and a device-status assessment that distinguishes an applicable exclusion, a device function requiring further pathway research, and an unresolved determination.
WHY
Why it matters
A submission assembled before device status is established may answer the wrong regulatory question.
Professional certification use alone does not establish device status; the intended purpose and applicable statutory exclusions matter.
One platform can contain functions with different regulatory statuses. A scheduling module does not settle the status of a diagnostic module.
FDA's January 2026 Clinical Decision Support Software guidance interprets the statutory exclusion for qualifying clinical decision support. Its January 29, 2026 issuance superseded the January 6 version.
Scope: This lesson teaches manufacturer-side assessment and documentation. It does not make a binding FDA determination, assign a device class, or establish that a particular submission is required.
KEY TERMS
Key Terms & Must-Know Facts
Table 1. Device-status reference vocabulary
Term
Working meaning
Assessment question
Device status
Whether the product or function falls within the statutory device definition after applicable exclusions.
Is this function a device?
Intended purpose
The purpose for which the product is intended, supported by its claims and use context.
What medical or nonmedical task is claimed?
Chemical action
A mechanism relevant to the statutory boundary between devices and other products.
Does chemical action within or on the body achieve the primary intended purposes?
Metabolism
A second mechanism boundary in the device definition.
Is achievement of the primary intended purposes dependent on metabolism?
Software function
A distinguishable capability with an identifiable purpose, inputs, processing, and outputs.
What exactly is this capability doing?
Statutory exclusion
A provision excluding a qualifying software function from the device definition.
Which provision applies, and are its conditions supported?
Administrative support
Operational activity such as scheduling rather than clinical interpretation.
Does this function manage operations or make a medical assessment?
Record management
Handling patient records; the applicable exclusion depends on its statutory conditions.
Is information handled without an additional interpretive purpose?
Clinical decision support
Software supporting clinical decisions; the name alone does not establish exclusion.
Does the actual function qualify under the statutory criteria?
Independent review
A clinician's ability to evaluate the basis for recommendations.
Can the user assess the reasoning rather than merely accept the result?
Classification
The later determination of the applicable device classification and controls.
Once device status is established, what regulatory category applies?
Assessment boundary
The defined function, version, users, and claims covered by the conclusion.
What is included, and what remains undecided?
Must-know facts:
Section 201(h)(1), codified at 21 U.S.C. 321(h)(1), supplies the device-definition starting point.
The definition addresses intended diagnostic, therapeutic, preventive, and structure-or-function purposes, subject to its mechanism limitations.
Section 520(o), codified at 21 U.S.C. 360j(o), excludes specified qualifying software functions.
A device-status conclusion and a submission-pathway conclusion are separate work products.
An exclusion requires supporting facts; a product category label is insufficient.
Missing information supports a documented open question, not a presumption of exclusion.
CORE
Core content
1.1.1.1 1. Start with purpose and mechanism
A Explanation
Decision conflict: choose a statutory assessment rather than a decision based on appearance, setting, or product name. WHY THIS IS TESTED: an early status error propagates into classification research, evidence planning, and submission selection.
Begin with a plain description: intended user, intended population, purpose, and how the product achieves that purpose. A diagnostic instrument may look unlike a therapeutic implant, yet both can require device analysis. Conversely, a product used in a hospital may serve only an administrative purpose.
For section 201(h)(1), evaluate the relevant intended medical purpose and the mechanism boundaries together. Do not treat the absence of chemical action as independently sufficient to establish device status. Likewise, do not conclude that any product involving chemistry cannot be a device: the statutory question concerns achievement of its primary intended purposes through chemical action within or on the body and dependence on metabolism.
When the description suggests drug, biologic, or combination-product issues, preserve that question for jurisdiction analysis. Do not force an uncertain mechanism into a convenient device pathway. See Fig 1.
Fig 1. Purpose before pathway Exam takeaway: Establish the function's status before selecting a submission strategy.
flowchart TD; A[Describe the product function] --> B[Identify intended purpose]; B --> C[Assess statutory mechanism boundaries]; C --> D[Evaluate applicable software exclusions]; D --> E[Document status or open question]; E --> F[Proceed to classification if appropriate];
Intended purpose at the workbench Exam takeaway: The physical object and its claimed purpose must be assessed together.
{"prompt":"Clean educational semi-flat illustration on a white background: a medical device regulatory affairs professional examines a handheld diagnostic instrument beside a purpose statement document and a simple patient-use sketch; cool blue and gray palette, no FDA logo, no invented authorization marks, no legal outcome, no figure numbers, all objects inside ample margins.","caption":"Intended purpose at the workbench","size":"1024x1024"}
Two independent questions Exam takeaway: A medical purpose and the statutory mechanism boundaries both require analysis.
flowchart TD; A[Product description] --> B[Intended purpose evidence]; A --> C[Mechanism evidence]; B --> D[Integrated statutory assessment]; C --> D; D --> E[Supported conclusion or unresolved issue];
Purpose and mechanism workflow Exam takeaway: Mechanism evidence cannot replace a clear statement of intended purpose.
1. Describe the claimed purpose.
2. Identify how the purpose is achieved.
3. Apply the definition and exclusions.
4. Record the conclusion and limits.
B Worked example
A company proposes a mechanical joint-support product for adults with impaired mobility. Its use illustration features a 68-year-old with osteoarthritis and hypertension; a mildly elevated glucose result appears in the background chart. The marketing draft calls the product a comfort accessory, but its proposed claims include supporting impaired joint function. No active ingredient is described.
Identify the task: assess device status, not choose a 510(k) type.
Extract key facts: the claimed structure-or-function purpose and mechanical action matter. Age, hypertension, and glucose do not establish the product's regulatory status.
Apply the rule: compare the actual purpose and mechanism with section 201(h)(1).
Eliminate: reject a non-device conclusion based solely on the phrase comfort accessory.
Verify: reconcile the proposed claims with the design description before documenting a device-status conclusion and beginning classification research.
C Exam trap
Wrong answer: classify by physical form alone. Why tempting: a familiar brace or instrument resembles products already sold as devices. Single eliminating clue: the task asks for statutory status, which requires the intended-purpose assessment.
D Checkpoint MCQ
Which information should be resolved first when the product description is incomplete?
A. The intended purpose and how it is achieved.
B. Whether a familiar product code appears in a database search.
C. Whether the product will be sold to hospitals.
D. Whether the sponsor prefers a 510(k) strategy.
Answer: A. A is attractive and correct because it supplies the facts needed for the definition. B is attractive because classification research is useful, but it cannot repair an undefined purpose. C is attractive because hospitals use devices, but the customer does not establish status. D is attractive because a pathway preference helps planning, but preference is not a statutory criterion.
If you missed this: Review Start with purpose and mechanism - focus on defining the product before researching its pathway.
1.1.1.2 2. Separate software functions before evaluating exclusions
A Explanation
Decision conflict: choose function-specific analysis rather than one regulatory label for an entire application. WHY THIS IS TESTED: a platform name can hide the difference between storing information and interpreting it.
Inventory each capability as an input-processing-output statement. For example, appointment details enter a scheduling function, which allocates a visit slot and displays a calendar entry. A different capability may accept clinical information and generate a patient-specific recommendation. These are separate assessment units even when they share a login.
Section 520(o) includes exclusions for specified administrative, record-related, and other software functions. The supplied blueprint identifies these categories but does not reproduce every statutory condition. Therefore, a category match is the beginning of the assessment: confirm the applicable provision and its conditions before finalizing a real product determination.
Choose wording that preserves the distinction: the scheduling function supports an administrative exclusion assessment; the interpretive function requires its own analysis. Avoid saying the application is excluded because it contains scheduling. See Fig 2.
Table 2. Separate information handling from interpretation
Function description
Initial assessment direction
Fact to confirm
Allocates appointment slots.
Evaluate administrative support exclusion.
No additional clinical interpretation within the assessed function.
Stores and retrieves patient records.
Evaluate applicable record-management conditions.
Actual operations and all relevant statutory conditions.
Uses patient findings to recommend a clinical action.
Evaluate device definition and qualifying CDS exclusion.
Inputs, intended user, clinical purpose, and reviewability.
Processes a medical image to identify suspected disease.
Assess a distinct medical interpretive function.
What image processing does and what medical claim it supports.
Fig 2. One platform, separate assessment units Exam takeaway: An administrative function cannot supply the exclusion rationale for a medical interpretive function.
flowchart TD; A[Shared software platform] --> B[Scheduling function]; A --> C[Record handling function]; A --> D[Clinical recommendation function]; B --> E[Administrative exclusion assessment]; C --> F[Record exclusion assessment]; D --> G[Device and CDS assessment];
Administrative workflow Exam takeaway: Scheduling activity is evaluated by its operational purpose.
{"prompt":"Educational semi-flat illustration on white: hospital scheduling employee using a calendar interface with appointment slots, beside a clinician waiting for a scheduled visit; no diagnosis, no risk score, no clinical recommendation on the interface, cool blue and gray, no readable personal data, no regulatory seals or figure numbers.","caption":"Administrative workflow","size":"1024x1024"}
Record handling without an added clinical conclusion Exam takeaway: Describe the actual record operations before invoking an exclusion.
{"prompt":"Educational semi-flat illustration: unchanged patient document pages move visually from a record folder to a computer record archive, a records professional compares identical pages side by side, white background, blue and gray, no diagnosis arrows, no invented regulatory conclusion, no readable identifiers, no figure numbering.","caption":"Record handling without an added clinical conclusion","size":"1024x1024"}
Function inventory workflow Exam takeaway: Record inputs, processing, and outputs separately for every material capability.
1. List distinct capabilities.
2. Describe each input and output.
3. Identify processing and purpose.
4. Test the relevant exclusion.
B Worked example
A clinic platform schedules visits, stores consultation notes, and produces patient-specific medication recommendations. A demonstration chart belongs to a 59-year-old with diabetes and chronic kidney disease; a normal temperature is highlighted. The sales deck calls the entire platform an electronic record system.
Identify the task: define the assessment units.
Extract key facts: scheduling, storage, and recommendation generation are distinct functions; the normal temperature is noise.
Apply the rule: evaluate each function against its purpose and potentially applicable exclusion.
Eliminate: reject a platform-wide exclusion based on the electronic record label.
Verify: obtain a function inventory showing whether the recommendation module adds clinical interpretation and how users receive its output.
C Exam trap
Wrong answer: treat every feature as record management. Why tempting: all features use the same patient chart. Single eliminating clue: one feature generates a new patient-specific recommendation.
D Checkpoint MCQ
A platform contains scheduling and a disease-detection function. What is the most appropriate next step?
A. Apply one administrative exclusion to the platform.
B. Assess the disease-detection function separately.
C. Choose the highest device class for every module.
D. Use the sponsor's platform category as the status conclusion.
Answer: B. A is tempting because scheduling is administrative, but its rationale does not extend automatically to detection. B is correct because the medical function needs its own analysis. C is tempting as a conservative shortcut, but classification must follow the applicable facts. D is tempting because a category label is convenient, but it does not establish statutory eligibility.
If you missed this: Review Separate software functions before evaluating exclusions - focus on the function as the assessment unit.
Quick Recall:
Professional certification setting alone establishes device status: false.
One excluded module excludes the whole platform: false.
1.1.1.3 3. Evaluate qualifying clinical decision support
A Explanation
Decision conflict: choose a criteria-based exclusion assessment rather than equating clinician involvement with non-device status. WHY THIS IS TESTED: a clinician can be present in a workflow while still relying primarily on an unexplained software recommendation.
The statutory non-device CDS analysis requires the applicable conditions to be satisfied together. At a practical screening level, examine whether the function processes medical images or relevant acquired signals; what patient or other medical information it uses; whether it supports or provides recommendations to a professional certification professional; and whether that professional can independently review the basis for those recommendations. This is a screening framework, not a substitute for the complete statutory text.
The January 2026 FDA guidance addresses these criteria. For this lesson, the decisive application skill is to inspect the basis available to the intended clinician. A button labeled explain, a confidence score, or a generic bibliography does not by itself demonstrate independent review. Ask what information the clinician can actually inspect and whether the use context permits meaningful evaluation.
Patient-facing recommendations require their own device-status analysis; they cannot borrow a clinician-focused exclusion merely because a clinician helped design the application. Time-critical use also requires particular attention to whether meaningful review can occur. Neither a failed CDS exclusion nor a time-critical label independently establishes a specific device class or submission requirement. Return to the definition and any other applicable provisions. See Fig 3.
Fig 3. Reviewability versus acceptance Exam takeaway: Clinician participation is different from the ability to independently assess a recommendation's basis.
flowchart TD; A[Recommendation presented] --> B{Basis independently reviewable}; B -->|Supported by facts| C[Evaluate remaining exclusion conditions]; B -->|Unsupported or unclear| D[Do not claim the CDS exclusion]; C --> E[Document criteria and evidence]; D --> F[Continue device-status assessment];
Meaningful clinician review Exam takeaway: Assess the information available to evaluate the recommendation, not merely the presence of an explanation icon.
{"prompt":"Two-panel educational illustration on white, blue and gray: left a clinician sees an unexplained recommendation card and a small confidence gauge; right the same clinician compares patient inputs, a recommendation, and a visible evidence explanation document side by side; no implication that either panel is FDA authorized, no readable patient data, no figure numbers.","caption":"Meaningful clinician review","size":"1024x1024"}
Users and use context change the assessment Exam takeaway: A clinician-focused exclusion cannot be transferred automatically to a patient-facing or urgent-use function.
flowchart TD; A[Clinical recommendation function] --> B[Intended clinician user]; A --> C[Intended patient user]; B --> D[Assess independent review in actual workflow]; C --> E[Assess definition and applicable exclusions separately]; D --> F[Consider time available for evaluation];
Patient-facing recommendation Exam takeaway: Intended users are assessment facts, not interchangeable labels.
{"prompt":"Respectful educational illustration of an adult patient using a phone at home showing a generic clinical recommendation card, with a separate small clinician workstation vignette to emphasize different users; white background, blue and gray, no emergency treatment advice, no personal data, no legal status labels, no FDA symbols or figure numbers.","caption":"Patient-facing recommendation","size":"1024x1024"}
CDS assessment workflow Exam takeaway: An unresolved exclusion condition remains an open regulatory question.
1. Identify inputs and processing.
2. Identify the intended user.
3. Inspect the recommendation's basis.
4. Evaluate review in the use context.
5. Document every applicable condition.
B Worked example
A software module recommends treatment options to clinicians for a 72-year-old with atrial fibrillation and chronic kidney disease. A stable hemoglobin result appears in the demonstration. The interface shows a confidence score and an accept button. The sponsor calls it transparent CDS, but the clinician cannot inspect why the patient's data produced the recommendation.
Identify the task: decide whether the stated facts support the qualifying CDS exclusion.
Extract key facts: clinician user and clinical recommendation are relevant; unavailable patient-specific reasoning is the critical gap.
Apply the rule: clinician involvement alone does not establish independent review of the basis.
Eliminate: reject confidence score, accept button, and the transparent label as substitutes for that ability.
Verify: request the explanation content, supporting information, and intended workflow; withhold an exclusion conclusion until the criteria are supported.
C Exam trap
Wrong answer: the clinician can override the recommendation, so the exclusion applies. Why tempting: override authority suggests professional control. Single eliminating clue: the clinician cannot independently review the recommendation's basis.
D Checkpoint MCQ
Which fact most directly addresses independent review?
A. The interface permits the clinician to reject the output.
B. The intended workflow provides an understandable basis the clinician can evaluate before deciding.
C. The output displays a high confidence value.
D. A clinical advisory board approved the interface terminology.
Answer: B. A is tempting because it preserves choice, but choice does not explain reasoning. B is correct because it addresses review of the basis in context. C is tempting because numerical precision suggests reliability, but confidence is not the underlying basis. D is tempting because expert involvement supports development, but it does not establish the end user's review ability.
If you missed this: Review Evaluate qualifying clinical decision support - focus on review of the basis rather than permission to override.
1.1.1.4 4. Document a bounded, reproducible determination
A Explanation
Decision conflict: choose a conclusion tied to evidence rather than a confident label that obscures missing information. WHY THIS IS TESTED: another regulatory professional must be able to reconstruct the assessment and recognize when a changed function requires reassessment.
A useful assessment records the function and version, intended purpose, intended users, inputs, processing, outputs, and use context. It then connects each relevant statutory element to supporting facts. Record the exclusion considered, the rationale for applying or rejecting it, and questions that remain unanswered.
Use three working outcomes: supported non-device or excluded-function conclusion; device-function conclusion requiring classification and pathway research; or unresolved status with a specific information request. These are documentation categories, not new FDA classifications. A sponsor assessment also does not constitute FDA clearance or approval.
Keep the next action proportional to the unresolved issue. A missing interface description calls for product information. A jurisdiction uncertainty may require appropriate FDA interaction. The neighboring lesson addresses combination-product jurisdiction; not every uncertainty requires a formal Request for Designation. See Fig 4.
Fig 4. Evidence-linked disposition Exam takeaway: The assessment should identify both the supported conclusion and the next unresolved task.
flowchart TD; A[Defined function and version] --> B[Map facts to statutory provisions]; B --> C{Evidence sufficient}; C -->|No| D[Specific information request]; C -->|Yes| E[Bounded status conclusion]; D --> B; E --> F[Document next regulatory action];
Assessment record Exam takeaway: A conclusion is useful when its facts, scope, and unresolved questions remain visible.
{"prompt":"Educational illustration of a manufacturer regulatory affairs professional assembling a device-status assessment at a desk: separate cards for scheduling, patient records, and clinical recommendations beside a versioned document with sections represented by blank lines; white background, crisp blue and gray semi-flat style, no invented legal citations, no FDA approval stamp, no figure numbering.","caption":"Assessment record","size":"1024x1024"}
Assessment completion workflow Exam takeaway: Close an evidence gap or preserve it explicitly instead of assuming eligibility.
1. Define the assessment boundary.
2. Cite the applicable provision.
3. Link facts to each condition.
4. State the conclusion and uncertainty.
5. Assign the next action.
B Worked example
A sponsor's platform stores records and provides an urgent deterioration recommendation. A demonstration uses a 76-year-old with heart failure and chronic obstructive pulmonary disease; a normal sodium value is emphasized. A competitor markets a similar product as non-device. The current sponsor has not supplied the intended response time or explanation screens.
Identify the task: finalize the device-status assessment without overstating certainty.
Extract key facts: the urgent recommendation is distinct from storage; response timing and review information are missing.
Apply the rule: evaluate the medical function and exclusion conditions using its own evidence.
Eliminate: reject competitor marketing and normal sodium as grounds for exclusion.
Verify: obtain the intended workflow and explanation content, record status as unresolved for that function, and preserve a separate assessment of storage.
C Exam trap
Wrong answer: conclude non-device because no evidence proves otherwise. Why tempting: it allows the project to proceed while information is incomplete. Single eliminating clue: eligibility for the asserted exclusion has not been supported.
D Checkpoint MCQ
Which conclusion best fits a function with unresolved intended users and unavailable explanation content?
A. Excluded, because it is described as CDS.
B. A device requiring PMA, because uncertainty suggests high risk.
C. Unresolved pending specified user and reviewability information.
D. Covered by the record-management conclusion for its host platform.
Answer: C. A is tempting because the CDS label suggests an exclusion, but the conditions remain unsupported. B is tempting as a conservative response, but uncertainty does not establish a PMA requirement. C is correct because it ties uncertainty to actionable missing facts. D is tempting because the functions share a platform, but that does not transfer the exclusion rationale.
If you missed this: Review Document a bounded, reproducible determination - focus on naming the evidence gap rather than guessing the outcome.
Quick Recall:
A status assessment is FDA authorization: false.
When evidence is missing, name the missing fact and its effect on the conclusion.
After a supported device-status conclusion, the next topic is classification and pathway research.
TRAPS
Exam Traps & Differentiators
Common traps & distractors:
Hospital use means device. Tempting because many hospital products are devices; the eliminating clue is a purely administrative purpose.
Digital means excluded. Tempting because software exclusions exist; the eliminating clue is an unassessed medical interpretive function.
Clinician approval means independent review. Tempting because the clinician makes the final decision; the eliminating clue is unavailable recommendation rationale.
Failed CDS exclusion means immediate 510(k). Tempting because the exclusion was the apparent barrier to regulation; the eliminating clue is that status, classification, and pathway remain separate determinations.
Table 3. Similar descriptions with different implications
Looks similar
Discriminating fact
Best assessment response
Records displayed versus records interpreted.
A new clinical conclusion is generated.
Assess the interpretive function separately.
Clinician can reject versus clinician can evaluate.
The basis is available and independently reviewable.
Document reviewability rather than override authority alone.
Clinician-facing versus patient-facing recommendations.
The intended recipient changes.
Reassess the applicable exclusion.
Non-device conclusion versus no submission conclusion.
The first concerns status; the second concerns premarket obligations.
Keep the decisions and rationales distinct.
Unsupported exclusion versus established device status.
A failed or incomplete exclusion does not complete the definition analysis.
Return to the statutory assessment.
If the scenario says:
One login and several capabilities → think function inventory.
Confidence score without underlying explanation → think reviewability evidence gap.
Patient is the intended recommendation recipient → think separate assessment of user-specific eligibility.
New medical claim added to a storage feature → think reassessment of the changed purpose.
Mechanism unclear → think jurisdiction question before pathway selection.
What is coming next: The supplied blueprint does not identify a specific pending rule or scheduled change for this topic. For future assessments, confirm the operative statutory provisions and guidance version, and revisit the rationale when claims, users, processing, or outputs change.
ALGO
Algorithm / Approach
Use this five-step approach to prepare the first regulatory assessment. It ends with a documented next action, not an assumed submission type.
1. Bound the function. Record version, users, purpose, inputs, processing, outputs, and context.
2. Apply the definition. Evaluate the intended medical purpose and statutory mechanism boundaries.
3. Evaluate exclusions. Match the actual software function to the applicable provision and support its conditions.
4. Resolve CDS questions. Examine inputs, recipient, recommendation purpose, and independent review in the intended workflow.
5. Document disposition. State the supported conclusion or specific unresolved issue and assign the next action.
Assessment record checklist
Function name, version, and assessment date.
Intended-purpose statement and source documents.
Mechanism description where relevant.
Applicable statutory provisions and exclusion considered.
Fact-by-fact rationale, including user and reviewability evidence where relevant.
Conclusion, boundaries, unresolved questions, and responsible next action.
QUIZ
Self-check quiz
Choose the most appropriate next step or conclusion. Questions 1-3 provide a short quick check; questions 4-5 integrate the workflow.
A sponsor describes software only as a professional certification productivity tool. What should regulatory affairs obtain first?
A. A competitor's product code. B. A function-level description of intended purpose, processing, and output. C. A preferred premarket submission date. D. A proposed 510(k) summary.
A platform's scheduling function is supported as excluded, but a second function generates diagnostic recommendations. Which conclusion is most defensible?
A. Both functions share the scheduling exclusion. B. Both functions require the same submission. C. The recommendation function needs a separate assessment. D. The combined platform label controls the assessment.
A clinician can dismiss a recommendation but cannot inspect its basis. Which issue remains unresolved for the qualifying CDS exclusion?
A. Whether the clinician can independently review the basis. B. Whether the clinician has override authority. C. Whether a human remains in the workflow. D. Whether the output is displayed electronically.
A proposed patient-facing function gives medical recommendations. The sponsor cites a clinician-focused CDS rationale from an earlier product. What is the best next step?
A. Retain the prior conclusion because the algorithm is unchanged. B. Retain it if clinicians helped develop the function. C. Require PMA because patients receive the output. D. Reassess the intended user, purpose, and applicable exclusions.
The intended response time and explanation interface for an urgent recommendation function are unavailable. What should the assessment record say?
A. Non-device until FDA objects. B. Unresolved, identifying the missing facts and their relevance. C. Class III because urgency implies the highest class. D. Excluded if its host platform also stores records.
ANSWERS
Answer key & explanations
1. Answer: B
A: Competitor research is tempting because it may reveal a familiar category, but the sponsor's own function remains undefined. B: Correct; purpose, processing, and output supply the starting facts. C: A target date is useful operationally, but it does not establish status. D: A summary is tempting as tangible progress, but drafting submission content precedes the necessary status determination.
If you missed this: Review Start with purpose and mechanism - focus on obtaining the facts needed for the definition.
2. Answer: C
A: Shared infrastructure makes this tempting, but exclusions do not transfer solely through platform membership. B: Uniform treatment seems administratively efficient, but obligations cannot be assigned before the individual assessments. C: Correct; the diagnostic recommendation has a distinct purpose. D: Product labels are convenient shorthand, but actual functions determine the assessment.
If you missed this: Review Separate software functions before evaluating exclusions - focus on distinct purposes within one platform.
3. Answer: A
A: Correct; dismissal does not demonstrate review of the basis. B: Override authority is tempting because it suggests control, but it is already present and does not resolve the gap. C: Human involvement is tempting because the exclusion concerns professional decision support, but presence alone is insufficient. D: Electronic display describes the medium, not the clinician's evaluative ability.
If you missed this: Review Evaluate qualifying clinical decision support - focus on understanding the basis rather than accepting or rejecting output.
4. Answer: D
A: Algorithm continuity is tempting because technical processing may be unchanged, but intended user remains a material assessment fact. B: Clinician development input is tempting as professional oversight, but it does not make the patient a clinician user. C: Patient use can increase concern, but it does not independently establish a PMA requirement. D: Correct; reassess the function against its actual intended use and potentially applicable provisions.
If you missed this: Review Evaluate qualifying clinical decision support - focus on the intended recipient of recommendations.
5. Answer: B
A: A default non-device conclusion is tempting because it permits progress, but it is unsupported. B: Correct; it preserves the evidence gap and defines the next task. C: A high-class default is tempting as caution, but urgency alone does not establish classification. D: The host platform's storage capability is tempting as an exclusion rationale, but it does not settle the recommendation function's status.
If you missed this: Review Document a bounded, reproducible determination - focus on actionable uncertainty rather than an assumed outcome.
RAPID
Rapid review / cheat-sheet
Assessment boundary → identify the function and version covered by the conclusion.
Purpose evidence → reconcile claims with the actual capability.
Mechanism uncertainty → preserve the jurisdiction question.
Shared interface → does not merge distinct regulatory rationales.
Exclusion claim → connect every applicable condition to supporting facts.
Reviewability evidence → inspect what the intended user can evaluate in context.
Unresolved result → specify the missing information and next action.
Completed status assessment → hand off to classification and pathway research when appropriate.
See also: Intended Use and Combination Product Jurisdiction; FDA Classification and Product Code Research. These neighboring topics extend this lesson's status determination into jurisdiction and classification work.
End of your free lesson
Keep going with the full US Medical Device Premarket Submissions Professional Certificate
You just studied the way members do, in the same lesson interface. Full access unlocks every lesson, the question bank and flashcards for a full year.