[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the AutoDose TPN (total parenteral nutrition calculator, Class C):

"Class C verification for the AutoDose TPN includes unit testing with statement coverage of at least 90%, branch coverage of at least 80%, and MC/DC coverage of at least 80% for safety-critical modules. Integration testing verifies all inter-unit interfaces. System-level verification is performed by independent personnel."

[Assistant]
Verdict: PASS
Note: Content correctly specifies full Class C rigor; correctly specifies independent review for Class C. Standards references are accurate.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadView DICOM (DICOM image viewer, Class A):

"System testing for the RadView DICOM is conducted per Clause 5.7.1 through 5.7.5. Test procedures verify end-to-end functionality of the DICOM image viewer against approved requirements. Detailed design verification (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6) are excluded as not applicable to Class A."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; includes all required verification levels. Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on development tools and tool qualification for Class A for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clause 5.1.4.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: Development of the BillingBridge Claims Processor uses Java/Spring Boot on Cloud (AWS). Build automation ensures reproducible compilation, and all toolchain versions are recorded as part of the configuration management baseline. Given the Class A classification, no formal tool qualification report is produced; tool defects are handled through the standard problem resolution process.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RetinaScan Pro (diabetic retinopathy screening AI, Class B):

"Compliance with IEC 62304 Clause 5.6.8 (performance benchmarking) and Clause 11.1 (continuous monitoring) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.6.8 and 11.1, neither of which exists. Clause 5.6 has 5.6.1 through 5.6.7 only. IEC 62304 has no Clause 11. All clause references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on configuration identification approach for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clauses 8.1, 8.1.1.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: Configuration items for the NeuroTune DBS Programmer Deep Brain Stimulator Programmer App are identified and placed under version control per Clause 8.1. The configuration baseline includes all items needed to reproduce the released software: source code, build scripts, third-party libraries, and the documentation set.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-005: "display update rate for Sleep Tracking Display App" (Category: functional)
Project: DreamLog Sleep Monitor | Sleep Tracking Display App | Class A
Visualizing sleep quality data for personal wellness awareness. Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The DreamLog Sleep Monitor shall update the displayed values on the BLE 5.2 at intervals no greater than the specified refresh period.
Rationale: Display freshness is critical for the Sleep Tracking Display App to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
Source: User need


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-DATA-001: "measurement record integrity" (Category: data)
Project: DialyFlow Dialysis Fluid Controller | Hemodialysis Fluid Controller Firmware | Class C
Controlling dialysate composition, flow rates, and ultrafiltration in hemodialysis. Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The DialyFlow Dialysis Fluid Controller shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a FMEA section on documenting failure modes and their effects for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: Each identified failure mode of the MedRef Clinical Reference App is documented per Clause 7.1.4 with the failure mode description, potential causes, local effects, end effects on the Clinical Drug Reference App, severity classification, and existing controls. The documentation supports risk control decision-making per Clause 7.2.1.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-001: "power-on self-test sequence" (Category: functional)
Project: NeuroTune DBS Programmer | Deep Brain Stimulator Programmer App | Class C
Programming stimulation parameters of implanted deep brain stimulators for Parkinson's disease management. Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The NeuroTune DBS Programmer startup sequence shall include diagnostic checks of all critical subsystems and report any detected faults before allowing operational use.
Rationale: Startup verification prevents the Deep Brain Stimulator Programmer App from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SEC-002: "cryptographic data security" (Category: security)
Project: DoseCalc Medication Calculator | Medication Dose Calculator App | Class B
Calculating weight-based medication doses for clinical prescribing support. Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The DoseCalc Medication Calculator shall encrypt patient-identifiable data at rest, ensuring that raw storage access cannot reveal protected health information.
Rationale: Encryption of stored patient data protects against unauthorized disclosure if the Medication Dose Calculator App storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Cryptographic implementation validated against NIST standards with no known vulnerabilities in the selected algorithm.
Source: Regulatory


[System] You are a requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-DATA-001: "measurement record integrity" (Category: data)
Project: GlucoSpot Continuous Glucose Display | CGM Display App | Class B
Displaying continuous glucose monitor readings with trend analysis and glucose range alerts. Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The GlucoSpot Continuous Glucose Display shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the CGM Display App are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the ChemoCalc (chemotherapy dose calculator, Class C):

"The ChemoCalc development follows full Class C rigor: detailed design documentation, unit testing with coverage targets (statement 90%, branch 80%, MC/DC 80%), integration testing of all interfaces, system testing, and independent verification. All activities are traceable to requirements."

[Assistant]
Verdict: PASS
Note: Content correctly specifies full Class C rigor; correctly specifies independent review for Class C. Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a FMEA section on failure mode identification approach for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: Software failure modes in the SunGuard UV Index Display are identified using a structured approach per Clause 7.1.2: each software item is analyzed for what could go wrong (the failure mode), why it could go wrong (the cause), and what would happen (the effect). SOUP component anomalies per Clause 7.1.3 are included as potential failure causes.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on change control process for StepSync Activity Tracker, a Class A Wellness Activity Display App. Reference IEC 62304 Clauses 8.2, 8.2.1.
Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

[Assistant] Content: The change control procedure for the StepSync Activity Tracker mandates that every modification to a controlled configuration item is initiated via a change request per Clause 8.2.1. Each request documents the proposed change, safety impact assessment, affected configuration items, and required re-verification for the Wellness Activity Display App.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clause 5.1.1.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: This Software Development Plan establishes the lifecycle framework for the TrainCert Staff Certification Tracker Training Certification System, defining all development activities, deliverables, and verification milestones in compliance with IEC 62304 Clause 5.1.1. As a Class A system that cannot contribute to a hazardous situation, the documentation scope is intentionally minimal, focusing on system-level verification and requirements traceability rather than detailed design or unit-level testing.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadView DICOM (DICOM image viewer, Class A):

"Maintenance activities follow IEC 62304:2020 Clause 6."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304:2020" which is incorrect. No 2020 edition exists. Current: IEC 62304:2006+AMD1:2015. All references must be corrected.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SRS section on latency and throughput requirements for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clause 5.2.2.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: The RadView DICOM Viewer shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Medical Image Viewer must sustain from input sources without data loss or processing backlog on Windows/macOS/Linux desktop.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the ThermoGuard (body temperature logger, Class A):

"Documentation is prepared in accordance with standard templates and guidelines. Review cycles are established at appropriate intervals for the body temperature logger."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "appropriate intervals" provide no project-specific information about the ThermoGuard body temperature logger. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on verification strategy for Class A -- system testing only for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clauses 5.7, 5.7.1.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: The NutriView Food Diary verification strategy relies solely on system testing, consistent with Class A requirements under IEC 62304. Each software requirement maps to at least one system test case, validated against the Nutritional Tracking Display App in its operational environment. No unit testing or integration testing is performed -- these activities are not mandated for Class A and would add unnecessary process overhead for the Nutritional Tracking Display App.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a FMEA section on risk control verification for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: Verification of AirSentry Urban Air Quality Station risk controls per Clause 7.3.1 is performed as part of the applicable verification level for the safety class. Each verified control has a documented result per Clause 7.3.3, confirming the Air Quality Monitoring Station Firmware meets the risk acceptability criteria.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-001: "startup diagnostic verification" (Category: functional)
Project: PainRelief PCA Pump Controller | PCA Pump Controller Firmware | Class C
Patient-controlled analgesic delivery with lockout intervals and cumulative dose limits. Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: Upon power-up, the PainRelief PCA Pump Controller shall execute a self-test sequence verifying the integrity of the syringe position encoder interface, internal memory, and output subsystem before entering operational mode.
Rationale: A power-on self-test confirms hardware and software readiness before the PCA Pump Controller Firmware begins use.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on hazard identification for the specific device for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: Software-related hazard causes for the CardioCloud ECG Analysis Service Cloud ECG Analysis SaMD are documented per Clause 7.1.2 and Clause 7.1.4. Risk control measures per Clause 7.2.1 address each identified cause through input validation, range checking, communication integrity verification, and fail-safe defaults.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on requirements verification approach for RespiRate Respiratory Monitor, a Class B Respiratory Rate Monitor Firmware. Reference IEC 62304 Clause 5.2.6.
Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

[Assistant] Content: Software requirements are verified per Clause 5.2.6 through formal review confirming each requirement is unambiguous, testable, consistent with system requirements, and traceable to its source. The RespiRate Respiratory Monitor requirements baseline is frozen only after successful review by the designated reviewers.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the VentAssist Pro (ICU ventilator controller, Class C):

"Unit verification for the VentAssist Pro follows Clause 5.5. Each unit has acceptance criteria per Clause 5.5.3 and additional criteria per Clause 5.5.4. Verification demonstrates MC/DC coverage for modules identified as safety-critical in the risk analysis."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the VentAssist Pro (ICU ventilator controller, Class C). Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a TRACE section on traceability scope including risk controls for SterilLog Sterilization Record System, a Class A Sterilization Record Logger. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Software logging sterilization cycle parameters from autoclaves. Records temperature, pressure, and time for compliance documentation.

[Assistant] Content: The SterilLog Sterilization Record System matrix traces two categories per Clause 5.7.1 and Clause 7.3.2: functional requirements (from system specification through design to test) and risk control requirements (from hazard analysis through SRS to verification). Both categories must show complete coverage before release of the Sterilization Record Logger.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on development platform and build infrastructure for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clause 5.1.4.
Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

[Assistant] Content: The DermaLens Teledermatology Platform is developed in Python (FastAPI + PyTorch) + React Native (mobile) targeting the Azure Kubernetes Service + CDN platform. Source code is maintained under version control with branching and tagging conventions defined in SOP-012. Build automation ensures reproducible compilation, and all toolchain versions are recorded as part of the configuration management baseline.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-DATA-001: "stored data corruption detection" (Category: data)
Project: WasteTrack Biohazard Logger | Biohazard Waste Tracking App | Class A
Logging and tracking biohazard waste container chain of custody. Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The WasteTrack Biohazard Logger shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on resource constraints and scalability for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: The PainRelief PCA Pump Controller shall operate within the memory, storage, and processing constraints of the MSP432 (dual-core safety) platform. Resource usage requirements are specified with numerical bounds and verified through profiling during system testing of the PCA Pump Controller Firmware.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on minimal deliverables list for Class A for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clause 5.1.8.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

[Assistant] Content: The BreathEasy Air Quality Display Class A documentation plan produces five controlled documents: this SDP, the Software Requirements Specification, the System Test Plan and Report, the Software Release Record, and the Risk Management File. No additional verification documents are required for the Environmental Air Quality Display.


[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the HydroLog (hydration tracking wellness app, Class A):

"The development plan references IEC 62304 Clause 11.1 and Clause 7.5 for the HydroLog."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 11.1 and 7.5, neither of which exists. IEC 62304 has no Clause 11. Clause 7 ends at 7.4. All clause references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on purpose of the SRS document for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 5.2.1.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: The SRS for the SunGuard UV Index Display documents every functional, performance, interface, and safety requirement governing the UV Exposure Display Firmware. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the PacePilot (pacemaker programmer, Class C):

"Architectural design follows IEC 62304-3 Clause 5.3 for Class C devices."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-3" which is incorrect. IEC 62304 has no Part 3. All references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on latency and throughput requirements for FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clause 5.2.2.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: The FleetTrack GPS Tracking Module shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Fleet GPS Tracking Firmware must sustain from GNSS module without data loss or processing backlog on nRF9160 (LTE-M SiP).


[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the AutoDose TPN (total parenteral nutrition calculator, Class C):

"The AutoDose TPN configuration management plan identifies all configuration items per Clause 8.1.1. SOUP items are tracked per Clause 8.1.2. Change control follows Clause 8.2 with traceability per Clause 8.2.4. Configuration status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the AutoDose TPN (total parenteral nutrition calculator, Class C). Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SAD section on architecture verification scope for BSACalc Body Surface Area Tool, a Class B BSA Calculator Web App. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

[Assistant] Content: Verification of the BSACalc Body Surface Area Tool architecture per Clause 5.3.6 is a phase gate requirement. The review confirms completeness of requirements coverage, correctness of interface definitions, and adequate risk control implementation in the BSA Calculator Web App design.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-004: "audit trail and data export" (Category: functional)
Project: WeightAlert Neonatal Scale | Neonatal Scale Firmware | Class B
Precision weight measurement for neonatal patients with change-rate alerting. Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: All processed measurements shall be stored with timestamps in a persistent log accessible through SPI for clinical review and regulatory audit.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for ECGInsight Rhythm Interpreter, a Class B ECG Interpretation Service. Reference IEC 62304 Clause 5.2.3.
Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

[Assistant] Content: Mitigations for ECGInsight Rhythm Interpreter STRIDE threats are expressed as software requirements per Clause 5.2.3 and verified through security testing. The ECG Interpretation Service implements authentication, encryption, integrity checking, and access control as documented in the SRS. Each mitigation is traced from the threat through the requirement to the verification evidence.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on minimal deliverables list for Class A for IncidentReport Clinical Event Logger, a Class A Incident Reporting System. Reference IEC 62304 Clause 5.1.8.
Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

[Assistant] Content: The IncidentReport Clinical Event Logger documentation set is limited to the deliverables required for Class A: the SDP, SRS, system test records, software release record, and the risk management file. No architecture document, detailed design specification, unit test report, or integration test report is produced for this Incident Reporting System.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the VentAssist Pro (ICU ventilator controller, Class C):

"The VentAssist Pro conforms to IEC 62304:2006+AMD1:2015. Safety classification per Clause 4.3 designates this ICU ventilator controller as Class C. Risk management follows ISO 14971:2019 with guidance from ISO/TR 24971:2020."

[Assistant]
Verdict: PASS
Note: Content correctly specifies full Class C rigor; uses the correct IEC 62304 citation; correctly references ISO 14971:2019. Standards references are accurate.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-002: "real-time performance requirement" (Category: performance)
Project: ConveyorGuard Safety Interlock System | Conveyor Safety Interlock Software | Class A
Monitoring safety interlocks and emergency stops on industrial conveyor systems. Safety PLC program monitoring conveyor belt guard positions, emergency stops, and light curtains. Functional safety application.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The ConveyorGuard Safety Interlock System shall process acquired data and update the output within the specified end-to-end latency from sample acquisition to display update.
Rationale: Real-time performance is critical for the Conveyor Safety Interlock Software to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the DermaScan AI (skin lesion classifier, Class B):

"In accordance with IEC 62304-4, verification activities include system testing."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-4" which is incorrect. IEC 62304 has no Part 4. All references must be corrected.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a TRACE section on risk control coverage verification for StepSync Activity Tracker, a Class A Wellness Activity Display App. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

[Assistant] Content: The StepSync Activity Tracker gap analysis per Clause 5.7.4 and Clause 7.3.2 verifies that the risk control traceability chain is complete. Every hazard in the risk management file that has a software control must trace to a verified requirement in the Wellness Activity Display App. Incomplete chains are flagged and resolved before release.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the HydroLog (hydration tracking wellness app, Class A):

"This plan is prepared in compliance with IEC 62304:2015 and ISO 13485:2016."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304:2015" which is incorrect. Wrong citation. Correct: IEC 62304:2006+AMD1:2015 (base standard from 2006, Amendment 1 in 2015). All references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on risk control requirements traceability for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.2.3.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: Software-implemented risk controls for the VitalBoard Patient Summary are documented as explicit requirements per Clause 5.2.3. Traceability from the ISO 14971 risk analysis through the SRS to verification test cases ensures that every risk control measure is implemented and verified in the Patient Summary Dashboard.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the HydroLog (hydration tracking wellness app, Class A):

"Software safety classification is performed per ISO 13485-2 Clause 4.3."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 13485-2" which is incorrect. ISO 13485 has no Part 2. All references must be corrected.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadView DICOM (DICOM image viewer, Class A):

"For the RadView DICOM, verification consists of executing system tests against the software requirements. Class A software does not require formal unit testing, integration testing, or independent verification. Test results are recorded per Clause 5.7.5 and any anomalies are handled through the problem resolution process per Clause 9."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SRS section on resource constraints and scalability for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 5.2.2.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The DoseLog Radiation Badge Reader shall operate within the memory, storage, and processing constraints of the Windows desktop platform. Resource usage requirements are specified with numerical bounds and verified through profiling during system testing of the Dosimetry Data Logger.


[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the PacePilot (pacemaker programmer, Class C):

"Per IEC 62304, the PacePilot software requirements are documented. Per IEC 62304, all requirements for the PacePilot are captured. Per IEC 62304, the requirements are recorded in the SRS. Per IEC 62304, each requirement is traceable to its source."

[Assistant]
Verdict: FAIL
Note: The documentation section exhibits repeated clause prefix. Multiple sentences begin with the same clause reference. Each sentence restates the same concept without adding information. Content should be consolidated and each sentence should contribute unique, specific information about the PacePilot.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on safety classification process and documentation for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 4.3.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: Software safety classification for the AnticoagCalc INR Dose Adjuster follows the procedure defined in IEC 62304 Clause 4.3. The classification considers whether the Anticoagulation Dosing Support Tool can contribute to a hazardous situation and, if so, whether external risk controls reduce the severity to non-serious injury. The result directly determines which IEC 62304 lifecycle activities are mandatory.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the NurseCall Hub (patient call system dashboard, Class A):

"Software problem resolution follows IEC 14971 Clause 9."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 14971" which is incorrect. Wrong prefix. The correct standard is ISO 14971, not IEC 14971. All references must be corrected.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the PhysioTrack Rehab (rehabilitation tracking system, Class B):

"The PhysioTrack Rehab development plan specifies Class B rigor: architectural design with interface documentation, integration testing of all inter-component interfaces, and system-level verification. Unit testing is recommended and will be performed for safety-related modules."

[Assistant]
Verdict: PASS
Note: Content correctly specifies Class B requirements. Standards references are accurate.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SAFE-001: "absence of safety-critical functions" (Category: safety)
Project: ClinTrial EDC Platform | Clinical Trial EDC Web Platform | Class A
Electronic capture and management of clinical trial data across multiple investigator sites. Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: No software path in the ClinTrial EDC Platform shall control therapeutic outputs, modify diagnostic results, or generate clinical alerts, confirming the validity of the Class A safety classification.
Rationale: Confirming the absence of safety-relevant functions validates the Class A classification under IEC 62304 Clause 4.3.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Clinical Trial EDC Web Platform.
Source: Regulatory


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the HydroLog (hydration tracking wellness app, Class A):

"The HydroLog development follows ISO 62304 for the software lifecycle."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 62304" which is incorrect. Wrong prefix. The correct standard is IEC 62304, not ISO 62304. All references must be corrected.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on problem reporting and investigation for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clauses 9.1, 9.2.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The problem resolution process for the HemaCount Digital Cell Counter follows Clauses 9.1 through 9.8. Each problem report is classified by severity, investigated for root cause, and resolved through the change control process. Records are maintained per Clause 9.5, and all resolutions are verified per Clause 9.7 before the IVD Digital Cell Counter Software baseline is updated.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a FMEA section on documenting failure modes and their effects for RetinaScan Diabetic Retinopathy Screener, a Class B Retinal Screening Software. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist review.

[Assistant] Content: The RetinaScan Diabetic Retinopathy Screener FMEA documents each failure mode per Clause 7.1.4, providing sufficient detail for risk evaluation: the software function affected, the failure mode, the cause(s), the effect on the Retinal Screening Software output, and the resulting hazard severity. This documentation is maintained in the risk management file.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on verification strategy for Class B -- integration and system testing for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clauses 5.6, 5.6.3, 5.7.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: The Class B verification strategy for the BalanceBoard Vestibular Trainer includes integration testing per Clause 5.6 and system testing per Clause 5.7. Integration tests validate the interaction between 4x load cells processing, USB communication, and output subsystems. System tests confirm end-to-end behavior of the Balance Training Platform Firmware against the SRS.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the CardioPulse Monitor (cardiac rhythm monitor, Class B):

"IEC 62311-1 Section 6.1 requires all software units to be verified."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62311-1" which is incorrect. IEC 62311 covers EMF exposure limits, not medical device software. All references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a TRACE section on purpose and scope of the traceability matrix for PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clause 5.7.1.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: Traceability for the PathSlide Digital Pathology Viewer per Clause 5.7.1 links system requirements to software requirements, software requirements to design elements, and design elements to verification test cases. The matrix serves as the primary evidence that the Digital Pathology Viewer verification is complete and that no requirement is unaddressed.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-DATA-003: "measurement data lifecycle" (Category: data)
Project: PathSlide Digital Pathology Viewer | Digital Pathology Viewer | Class A
Display of digitized pathology slides for reference viewing. Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: Measurement records stored by the Digital Pathology Viewer shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Digital Pathology Viewer.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RetinaScan Pro (diabetic retinopathy screening AI, Class B):

"This plan is prepared in compliance with IEC 62311-1 and ISO 13485:2016."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62311-1" which is incorrect. IEC 62311 covers EMF exposure limits, not medical device software. All references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-004: "continuous data sampling from ingestible temperature capsule RF receiver" (Category: functional)
Project: ThermoWatch Core Temperature Monitor | Core Temperature Monitor Firmware | Class B
Continuous core body temperature monitoring with trend display and threshold alerts. Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: Data from the ingestible temperature capsule RF receiver shall be acquired by the ThermoWatch Core Temperature Monitor at the configured rate, with each sample timestamped and queued for processing.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Core Temperature Monitor Firmware.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on change control process for FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: Changes to the FleetTrack GPS Tracking Module software baseline require a documented change request approved before implementation. The change control process per Clause 8.2 includes impact assessment on safety, regression risk evaluation, and verification of the change before integration into the controlled baseline.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the DermaScan AI (skin lesion classifier, Class B):

"The DermaScan AI addresses IEC 62304 Clause Annex A.1 for deployment validation and Clause 5.4.5 for data archival."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 5.4.5, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. Clause 5.4 has 5.4.1 through 5.4.4 only. All clause references must be corrected.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadView DICOM (DICOM image viewer, Class A):

"Verification activities follow IEC 62304 Clause 5.7.6 for post-market surveillance."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.7.6 which does not exist. Clause 5.7 has 5.7.1 through 5.7.5 only. The reference must be corrected to a valid clause number.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a FMEA section on risk control verification for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: The LabStream LIS Middleware risk control verification per Clause 7.3.1 exercises each control measure in isolation and in the context of the complete Laboratory Information Middleware. Clause 7.3.3 documentation records the verification method, the test result, and the conclusion regarding the control's effectiveness.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on system boundaries and external dependencies for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clause 5.2.2.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: The BalanceBoard Vestibular Trainer software boundary encompasses the Balance Training Platform Firmware application executing on STM32H7 + display. External dependencies include 4x load cells hardware and display output. These external systems are treated as black boxes at the software boundary, with interface requirements specified in this SRS.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on risk management integration into the lifecycle for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clauses 7.1, 7.1.1.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

[Assistant] Content: The PressoTrack Blood Pressure Trending risk management process is concurrent with development, not sequential. Software causes of hazardous situations are identified per Clause 7.1 and documented per Clause 7.1.4. Risk controls are implemented as software requirements and verified through the applicable testing levels for the Ambulatory Blood Pressure Monitor Firmware.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SRS section on purpose of the SRS document for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clause 5.2.1.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: The SRS for the PostureGuard Desk Monitor documents every functional, performance, interface, and safety requirement governing the Posture Wellness Display Software. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadBeam Planner (radiation therapy planning system, Class C):

"Software development follows IEC 62304 Clause 5.1.12 requirements for continuous monitoring."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.1.12 which does not exist. Clause 5.1 has 5.1.1 through 5.1.11 only. The reference must be corrected to a valid clause number.


[System] You are a requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-FUNC-003: "display update rate for Cold Chain Temperature Logger" (Category: functional)
Project: FridgeGuard Temperature Logger | Cold Chain Temperature Logger | Class A
Continuous logging and display of storage temperatures for compliance documentation. Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: The FridgeGuard Temperature Logger display shall present current readings on 1-Wire within the specified maximum update latency.
Rationale: Display freshness is critical for the Cold Chain Temperature Logger to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the MedInventory (medical supply tracking system, Class A):

"In accordance with ISO 13485-1, verification activities include system testing."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 13485-1" which is incorrect. ISO 13485 is a single-part standard. The correct citation is ISO 13485:2016. All references must be corrected.


[System] You are a requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-SAFE-001: "safety classification confirmation for Class A" (Category: safety)
Project: AutoclaveLog Cycle Recorder | Sterilization Cycle Data Logger | Class A
Recording and reporting autoclave sterilization cycle parameters. PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: No software path in the AutoclaveLog Cycle Recorder shall control therapeutic outputs, modify diagnostic results, or generate clinical alerts, confirming the validity of the Class A safety classification.
Rationale: The Class A classification of the Sterilization Cycle Data Logger depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Sterilization Cycle Data Logger.
Source: Regulatory


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the PacePilot (pacemaker programmer, Class C):

"Unit verification for the PacePilot follows Clause 5.5. Each unit has acceptance criteria per Clause 5.5.3 and additional criteria per Clause 5.5.4. Verification demonstrates MC/DC coverage for modules identified as safety-critical in the risk analysis."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PacePilot (pacemaker programmer, Class C). Standards references are accurate.


[System] You are a medical device regulatory standards expert with comprehensive knowledge of IEC 62304, ISO 14971, ISO 13485, IEC 62366-1, IEC 82304-1, IEC 81001-5-1, IEC 60601-1 and its sub-parts, and associated regulatory guidance. Provide accurate standards references. Never fabricate clause numbers or standard sub-parts.

[User] Is integration testing required for Class A software?

[Assistant] No. Integration testing (Clause 5.6) is NOT required for IEC 62304 Class A software. Class A verification is limited to system-level testing per Clause 5.7. Integration testing becomes required starting at Class B.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a THREAT section on system description for threat modeling for StrokeAlert CT Perfusion Analyzer, a Class C AI Stroke Triage CT Perfusion SaMD. Reference IEC 62304 Clause 5.2.1.
Time-critical cloud SaMD processing CT perfusion scans to generate ischemic core and penumbra maps for acute stroke triage. Results pushed to mobile app within 5 minutes.

[Assistant] Content: The StrokeAlert CT Perfusion Analyzer threat model system description per IEC 81001-5-1:2021 identifies the AI Stroke Triage CT Perfusion SaMD as the subject, with trust boundaries at each external interface. Assets include software integrity, data confidentiality, and service availability during Rapid automated CT perfusion analysis generating ischemic core and penumbra maps for acute stroke treatment decisions.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SAD section on purpose of the architecture document for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clause 5.3.1.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: This SAD transforms the DoseCalc Medication Calculator software requirements into a design architecture per Clause 5.3.1. The Medication Dose Calculator App is decomposed into software items with clearly defined boundaries, interfaces, and data flows, supporting both implementation and verification activities.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SRS section on external system communication requirements for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clause 5.2.2.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: The DoseCalc Medication Calculator Medication Dose Calculator App external communication requirements cover data exchange with remote systems. Each requirement specifies the message format, transport protocol, retry policy, and failure mode behavior, ensuring the Medication Dose Calculator App degrades safely if communication is disrupted.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the RadBeam Planner (radiation therapy planning system, Class C):

"In accordance with ISO 14901, verification activities include system testing."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14901" which is incorrect. ISO 14901 does not exist. The risk management standard is ISO 14971:2019. All references must be corrected.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on system test execution and acceptance for Class A for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clauses 5.7, 5.7.4.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: Acceptance of the AirSentry Urban Air Quality Station is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Air Quality Monitoring Station Firmware.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the NeuroStim Programmer (neurostimulator programmer, Class C):

"All verification for the neurostimulator programmer follows IEC 62304-2 requirements."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-2" which is incorrect. IEC 62304 has no Part 2. It is a single-part standard. All references must be corrected.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on requirements verification approach for PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clause 5.2.6.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Requirements verification for the PharmaSafe CDSS is conducted per Clause 5.2.6 before the requirements baseline is established. The review confirms completeness, consistency, and testability. Any requirement failing these criteria is returned for rework before the Clinical Decision Support System proceeds to design.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the GlucoTrack CGM (continuous glucose monitor display, Class B):

"REQ-SRS-023: The GlucoTrack CGM shall validate all input data against defined ranges before processing. Out-of-range values shall be rejected with an error code. Acceptance criterion: submit boundary values and verify correct acceptance/rejection. Priority: Mandatory. Source: Risk control."

[Assistant]
Verdict: PASS
Note: Content requirement is properly structured with measurable acceptance criteria; risk management content follows ISO 14971 framework. Standards references are accurate.


[System] You are an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-002: "resource utilization limits" (Category: performance)
Project: WaveReview EEG Archive Viewer | EEG Archive Viewer | Class A
Read-only playback and display of archived EEG recordings. Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

Output fields:
Description: 1-2 specific, measurable sentences
Rationale: 1 sentence explaining why this requirement exists
Priority: "Mandatory" or "Desirable" or "Optional"
Acceptance Criterion: Measurable test criterion
Source: "User need" or "System requirement" or "Risk control" or "Regulatory"

[Assistant]
Description: Peak memory consumption of the EEG Archive Viewer shall not exceed the allocated budget, with sufficient margin for stack overflow protection.
Rationale: Memory constraints are fixed by the Windows/Linux desktop hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


[System] You are an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the LabView Portal (read-only lab results viewer, Class A):

"The LabView Portal software verification plan specifies system testing as the sole verification activity. Clause 5.5 (unit verification) and Clause 5.6 (integration testing) do not apply to Class A. Test cases verify all software requirements."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. Standards references are accurate.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the SleepWell (sleep quality display app, Class A):

"All source code modules shall undergo unit testing using xUnit framework with coverage reporting."

[Assistant]
Verdict: FAIL
Note: Content mandates unit testing for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Unit verification (Clause 5.5) is not required for Class A.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on system test execution and acceptance for Class A for FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clauses 5.7, 5.7.4.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: The FleetTrack GPS Tracking Module system test suite runs on nRF9160 (LTE-M SiP) exercising all functional, performance, and interface requirements. Clause 5.7.4 verification confirms every SRS requirement has at least one passing system test. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are outside the scope of Class A verification and are not executed.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the CaloriePal (nutrition tracking app, Class A):

"Verification planning for the CaloriePal scopes testing to system level only, consistent with Class A requirements. The verification plan references Clause 5.7 and defines acceptance criteria for each software requirement. Code coverage analysis is not required and is not included in the plan."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; limits verification to system testing per Clause 5.7. Standards references are accurate.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on configuration identification approach for CardioRhythm ECG Analyzer, a Class B Single-Lead ECG Device Firmware. Reference IEC 62304 Clauses 8.1, 8.1.1.
Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay diagnosis.

[Assistant] Content: Configuration items for the CardioRhythm ECG Analyzer Single-Lead ECG Device Firmware are identified and placed under version control per Clause 8.1. The configuration baseline includes all items needed to reproduce the released software: source code, build scripts, third-party libraries, and the documentation set.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the DermaScan AI (skin lesion classifier, Class B):

"Software requirements for the DermaScan AI are defined per Clause 5.2.1 and documented with the content required by Clause 5.2.2. Risk control measures are included in requirements per Clause 5.2.3. Requirements are verified per Clause 5.2.6."

[Assistant]
Verdict: PASS
Note: Content risk management content follows ISO 14971 framework. Standards references are accurate.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on development platform and build infrastructure for WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clause 5.1.4.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

[Assistant] Content: The WeatherNode Microclimate Station build environment uses C (embedded) on STM32WL (LoRa SoC). Continuous integration builds execute on every commit, ensuring early detection of compilation errors and regression failures. Toolchain versions are locked to the configuration baseline and recorded in the Software Configuration Management Plan.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a THREAT section on STRIDE threat categories applied to the device for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.2.2.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: STRIDE threat analysis for the PaceSet Pacemaker Programmer identifies specific threats at each data flow crossing a trust boundary. For the proprietary RF interface: Spoofing is addressed by authentication, Tampering by integrity checks, Information Disclosure by encryption, and Denial of Service by rate limiting and timeout detection.


[System] You are a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on requirements elicitation and documentation for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

[Assistant] Content: Requirements for the VitalPulse SpO2 Monitor are elicited from system-level specifications, the ISO 14971 risk management file, and user needs analysis. Each software requirement is documented per Clause 5.2.2 with a unique identifier, rationale, acceptance criteria, and traceability to its source.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a FMEA section on risk control measures and implementation for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: The AutoclaveLog Cycle Recorder risk controls per Clause 7.2.1 address each failure mode with unacceptable residual risk. Software-implemented controls per Clause 7.2.2 include defensive coding measures, plausibility checks, and safe-state transitions. Each control is documented as a software requirement and verified for the Sterilization Cycle Data Logger.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the FetaSound (fetal heart rate monitor, Class B):

"This plan is prepared in compliance with ISO 14901 and ISO 13485:2016."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14901" which is incorrect. ISO 14901 does not exist. The risk management standard is ISO 14971:2019. All references must be corrected.


[System] You are an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on configuration identification approach for PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clauses 8.1, 8.1.1.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: All artifacts produced during PathSlide Digital Pathology Viewer development are placed under configuration control per Clause 8.1. Configuration items include source files, build definitions, documentation, test scripts, and SOUP component packages. Each item is uniquely identified by a repository path and immutable revision hash.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the MedInventory (medical supply tracking system, Class A):

"Release activities follow standard practices to ensure quality and traceability. The release package is prepared as needed for regulatory submission."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed", "standard practices" provide no project-specific information about the MedInventory medical supply tracking system. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the NurseCall Hub (patient call system dashboard, Class A):

"The NurseCall Hub integration test suite validates all APIs, shared memory interfaces, and IPC mechanisms between software items."

[Assistant]
Verdict: FAIL
Note: Content mandates integration testing of all interfaces for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Integration testing (Clause 5.6) is not required for Class A.


[System] You are a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

[User]
Review this documentation excerpt for the ChemoCalc (chemotherapy dose calculator, Class C):

"Compliance with IEC 62304 Clause Annex B.3 is demonstrated through user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause Annex B.3 which does not exist. IEC 62304 annexes are not cited as requirements. The reference must be corrected to a valid clause number.