[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 GaitSense Walking Analysis, a Class B Gait Analysis Insole Firmware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

[Assistant] Content: Traceability for the GaitSense Walking Analysis Gait Analysis Insole Firmware covers all software requirements per Clause 5.7.1 and all software-implemented risk controls per Clause 7.3.2. The combined matrix provides a single view of verification completeness for functional and safety aspects.


[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 verification and traceability for PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Risk control verification for the PharmaSafe CDSS per Clause 7.3.1 is performed as part of the applicable testing levels. Each risk control measure is traced per Clause 7.3.2 from the ISO 14971 risk analysis through the SRS to the test result confirming its implementation in the Clinical Decision Support System.


[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 RadBeam Planner (radiation therapy planning system, Class C):

"The RadBeam Planner addresses IEC 62304 Clause 11.1 for performance benchmarking and Clause 5.8.9 for operational qualification."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 11.1 and 5.8.9, neither of which exists. IEC 62304 has no Clause 11. Clause 5.8 has 5.8.1 through 5.8.8 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 DermaScan AI (skin lesion classifier, Class B):

"The DermaScan AI software development conforms to IEC 62304-5, with risk management per ISO 14971:2019."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-5" which is incorrect. IEC 62304 has no Part 5. 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 RadBeam Planner (radiation therapy planning system, Class C):

"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 RadBeam Planner radiation therapy planning system. 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 SRS section on baseline security requirements for HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clause 5.2.2.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

[Assistant] Content: Baseline security requirements for the HumidityMap Room Condition Logger ensure the Environmental Condition Logger protects user data, resists unauthorized access, and maintains audit trails. Data communicated via web dashboard is encrypted. Access is controlled through authentication mechanisms appropriate to the deployment environment.


[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 PillRemind (medication reminder app, Class A):

"Hazard analysis for the PillRemind identifies that incorrect display of measurement values could mislead the clinician. Risk control measures include input validation (REQ-SRS-023), display range checking, and a visual indicator when data is stale. Residual risk is acceptable per the risk management plan."

[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-FUNC-003: "measurement data archival" (Category: functional)
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: All processed measurements shall be stored with timestamps in a persistent log accessible through BLE 5.0 (CGM receiver) for clinical review and regulatory audit.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the CGM Display App.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


[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 SOUP identification and management for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 8.1.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: Identification of SOUP for the GrowthChart Pediatric Viewer follows Clause 8.1.2. Each SOUP component record includes title, version, supplier, intended function within the Growth Chart Display App, and a reference to the anomaly evaluation performed per Clause 7.1.3. SOUP updates are managed through the change control process per Clause 8.2.


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

[User]
Expand requirement SRS-PERF-001: "resource utilization limits" (Category: performance)
Project: TransVent Transport Ventilator | Transport Ventilator Firmware | Class C
Mechanical ventilation during patient transport in pre-hospital and inter-hospital settings. Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

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 Transport Ventilator Firmware shall not exceed the allocated budget, with sufficient margin for stack overflow protection.
Rationale: Exceeding memory limits could cause undefined behavior in the Transport Ventilator Firmware, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


[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-006: "output refresh interval for FridgeGuard 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: Output presentation on the 1-Wire shall refresh at the configured interval, reflecting the most recent processed data from the Cold Chain Temperature Logger pipeline.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
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 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 Class A classification justification and implications for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 4.3.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: Under IEC 62304 Clause 4.3, the SunGuard UV Index Display is classified as Safety Class A. The UV Exposure Display Firmware is a purely informational system for Passive display of UV index for personal awareness with no control over therapeutic delivery, diagnostic decision-making, or life-sustaining functions. Software failure would result in loss of informational display, not patient harm.


[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 HydroLog follows the software lifecycle. The HydroLog implements the lifecycle processes. The HydroLog adheres to the lifecycle model. The HydroLog conforms to the lifecycle framework."

[Assistant]
Verdict: FAIL
Note: The documentation section exhibits repeated project name. The project name 'HydroLog' appears excessively. Sentences repeat the same assertion about the hydration tracking wellness app in different words. Content should be consolidated and each sentence should contribute unique, specific information about the HydroLog.


[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-SEC-001: "cryptographic data security" (Category: security)
Project: RespiRate Respiratory Monitor | Respiratory Rate Monitor Firmware | Class B
Continuous respiratory rate monitoring with alarm generation for abnormal rates. Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

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 RespiRate Respiratory Monitor 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 Respiratory Rate Monitor Firmware 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 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 EchoAssist (echocardiogram analysis aid, Class B):

"Quality activities are performed in line with relevant standards and guidelines. Reviews and approvals follow established organizational procedures."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "relevant standards", "established organizational procedures" provide no project-specific information about the EchoAssist echocardiogram analysis aid. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


[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-PERF-002: "RAM and storage constraints" (Category: performance)
Project: FleetTrack GPS Tracking Module | Fleet GPS Tracking Firmware | Class A
Real-time GPS tracking and geofence monitoring of fleet vehicles. Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

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 FleetTrack GPS Tracking Module memory footprint on nRF9160 (LTE-M SiP) shall remain within specified limits under worst-case operational scenarios.
Rationale: Exceeding memory limits could cause undefined behavior in the Fleet GPS Tracking Firmware, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-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 RadView DICOM (DICOM image viewer, Class A):

"REQ-SRS-012: The RadView DICOM shall log all user actions with timestamps in an audit trail stored in non-volatile memory. The audit trail shall retain at least 10,000 entries. Acceptance criterion: verify log persistence across power cycles and entry count capacity. Priority: Mandatory. Source: Regulatory."

[Assistant]
Verdict: PASS
Note: Content requirement is properly structured with measurable acceptance criteria. 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] What sub-clauses exist under IEC 62304 Clause 5.2?

[Assistant]
IEC 62304 Clause 5.2 (Software requirements analysis) contains the following sub-clauses:

- Clause 5.2: Software requirements analysis
- Clause 5.2.1: Define and document software requirements from system requirements
- Clause 5.2.2: Software requirements content
- Clause 5.2.3: Include risk control measures in software requirements
- Clause 5.2.4: Re-evaluate medical device risk analysis
- Clause 5.2.5: Update system requirements
- Clause 5.2.6: Verify software requirements

These are the only valid sub-clauses under 5.2. No additional sub-clauses exist.


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

[User]
Expand requirement SRS-FUNC-003: "device configuration management" (Category: functional)
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: Configuration changes to the PathSlide Digital Pathology Viewer shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Configurable parameters allow the Digital Pathology Viewer to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


[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 data format and interoperability requirements for AuditTrail QMS Event Logger, a Class A QMS Audit Trail Service. Reference IEC 62304 Clause 5.2.2.
Microservice capturing and storing quality management system audit events. Logging and reporting only.

[Assistant] Content: The AuditTrail QMS Event Logger QMS Audit Trail Service data exchange formats are specified in this SRS with field-level definitions, data types, units, and valid ranges. The software performs schema validation on all incoming data from REST API before processing.


[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 data processing and transformation requirements for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clause 5.2.2.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

[Assistant] Content: The AssetTrack Equipment Inventory data pipeline requirements specify end-to-end data flow from camera barcode scanner through processing to output on REST API. Requirements include input validation, range checking, unit conversion, and output formatting for Tracking location and status of medical equipment for inventory management.


[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] List all valid IEC 62304 sub-clauses under Clause 5.4 and their subjects.

[Assistant]
IEC 62304 Clause 5.4 (Software detailed design) contains the following sub-clauses:

- Clause 5.4: Software detailed design
- Clause 5.4.1: Subdivide software into software units
- Clause 5.4.2: Develop detailed design for each software unit
- Clause 5.4.3: Develop detailed design for interfaces
- Clause 5.4.4: Verify detailed design

These are the only valid sub-clauses under 5.4. No additional sub-clauses exist.


[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-002: "data integrity validation" (Category: data)
Project: WoundTrack Healing Analyzer | Wound Assessment App | Class B
Photographic wound measurement and healing progress tracking for clinical review. Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

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 WoundTrack Healing Analyzer shall detect corrupted measurement records through integrity checking and flag affected entries for review.
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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-007: "audit trail and data export" (Category: functional)
Project: GasMonitor Anesthetic Gas Logger | Anesthetic Gas Concentration Logger | Class A
Recording waste anesthetic gas levels for occupational safety documentation. Software logging waste anesthetic gas concentrations in operating rooms for occupational safety compliance. Recording only.

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 Anesthetic Gas Concentration Logger shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via RS-232.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Anesthetic Gas Concentration Logger.
Priority: Desirable
Acceptance Criterion: Logged data is retrievable after power cycle, with all timestamps accurate to within 1 second of the reference clock.
Source: User need


[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 WoundTrack (wound measurement imaging system, Class B):

"Configuration management for the WoundTrack follows Clause 8. Configuration items are identified per Clause 8.1.1, SOUP is identified per Clause 8.1.2, and change control is managed per Clause 8.2. Status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the WoundTrack (wound measurement imaging system, Class B). 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 scope boundaries of the software system for PulseRing Smart Ring Monitor, a Class B Wearable Smart Ring Firmware + Companion App. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

[Assistant] Content: The PulseRing Smart Ring Monitor software boundary includes the application firmware, configuration data, and all SOUP components deployed on nRF5340 (firmware) + iOS/Android (app). Hardware components, operating system kernels supplied by the platform vendor, and remote services accessed via cloud sync API are excluded from the software lifecycle activities defined here, though their influence on software behavior is addressed in the risk analysis.


[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 GlucoTrack CGM (continuous glucose monitor display, Class B):

"Integration testing for the GlucoTrack CGM covers all interfaces between software items per Clause 5.6.1 through 5.6.7. Test content addresses data flow, timing, and error handling at each interface. Regression testing is conducted per Clause 5.6.6 after each integration step."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the GlucoTrack CGM (continuous glucose monitor display, Class B). 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 PillRemind (medication reminder app, Class A):

"Safety classification of the PillRemind is performed per Clause 4.3. The quality management system meets Clause 4.1. Risk management is applied per Clause 4.2 in conjunction with ISO 14971:2019."

[Assistant]
Verdict: PASS
Note: Content correctly references ISO 14971:2019. 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 development platform and build infrastructure for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clause 5.1.4.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: Source code for the WaveReview EEG Archive Viewer EEG Archive Viewer is written in Python/PyQt and compiled for Windows/Linux desktop. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


[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: "alarm generation and notification" (Category: functional)
Project: ChemoFlow Infusion Controller | Chemotherapy Infusion Pump Firmware | Class C
Precision-controlled chemotherapy drug infusion with dose-error detection and safety interlocks. Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

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: Alarm thresholds shall be configurable per clinical protocol. The ChemoFlow Infusion Controller shall trigger alerts within the maximum allowable latency of a threshold crossing.
Rationale: Alarm functionality is a safety-critical feature of the Chemotherapy Infusion Pump Firmware that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


[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 verification strategy addresses only system testing as mandated for Class A software per IEC 62304. Each software requirement has at least one corresponding system test case. No unit or integration testing is specified because Class A software cannot contribute to a hazardous situation."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; risk management content follows ISO 14971 framework. 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 SRS section on functional requirements overview for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 5.2.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: Functional requirements for the CogniTest Cognitive Assessment App are derived from the system requirements for Administering and scoring standardized cognitive screening tests for clinical neuropsychological assessment and from risk control measures identified in the ISO 14971 analysis. Each requirement specifies a single function of the Cognitive Assessment Application with measurable acceptance 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):

"Hazard analysis for the NurseCall Hub identifies that incorrect display of measurement values could mislead the clinician. Risk control measures include input validation (REQ-SRS-023), display range checking, and a visual indicator when data is stale. Residual risk is acceptable per the risk management plan."

[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 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):

"The CardioPulse Monitor addresses IEC 62304 Clause 5.4.5 (detailed design verification) through formal review."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.4.5 which does not exist. Clause 5.4 has 5.4.1 through 5.4.4 only. The reference must be corrected to a valid clause number.


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

[User]
Expand requirement SRS-INTF-002: "clinical system integration interface" (Category: interface)
Project: GaitSense Walking Analysis | Gait Analysis Insole Firmware | Class B
Quantitative gait analysis using instrumented insoles for orthopedic and rehabilitation assessment. Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

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 Gait Analysis Insole Firmware shall support bidirectional data exchange with external systems over BLE 5.0.
Rationale: External system connectivity is required for the Gait Analysis Insole Firmware to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


[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 milestones and phase transition criteria for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clause 5.1.1.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

[Assistant] Content: Milestones governing the CochleaMap CI Fitting Software lifecycle include Requirements Baseline, Architecture Baseline, Implementation Complete, Verification Complete, and Release Readiness. Each milestone has defined entry and exit criteria documented in this plan. No milestone can be declared complete while open problem reports of severity "major" or higher remain unresolved.


[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):

"The NeuroStim Programmer addresses IEC 62304 Clause Annex A.1 for continuous monitoring and Clause 5.9 for automated regression testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 5.9, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. Clause 5 ends at 5.8. 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 SleepWell (sleep quality display app, Class A):

"For the SleepWell, ISO 14971:2019 risk management is integrated with the IEC 62304 software lifecycle. Risk control measures identified in the risk analysis are incorporated as software requirements per Clause 5.2.3. The medical device risk analysis is re-evaluated per Clause 5.2.4 after requirements changes."

[Assistant]
Verdict: PASS
Note: Content correctly references ISO 14971:2019; risk management content follows ISO 14971 framework. 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 change control and trend analysis for problems for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clauses 9.4, 9.6.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: Corrections to the AutoclaveLog Cycle Recorder follow the change control process per Clause 9.4, with regression testing proportional to the scope of the change. Problem reports are periodically analyzed for trends per Clause 9.6 to identify systemic issues in the development process that might affect the quality of the Sterilization Cycle Data 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 risk control verification and traceability for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Verification of risk controls for the InhaleSense Smart Inhaler Tracker follows Clause 7.3.1. Each control implemented in software has a corresponding test case that demonstrates the hazardous condition is mitigated. Traceability records per Clause 7.3.2 document the chain from hazard through requirement to verification evidence.


[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 ThermoGuard (body temperature logger, Class A):

"The ThermoGuard software development conforms to ISO 62304, with risk management per ISO 14971:2019."

[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 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 PillRemind (medication reminder app, Class A):

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

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-5" which is incorrect. IEC 62304 has no Part 5. 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 safety requirements for Class A -- confirms no safety functions for AutoHUD Heads-Up Display Controller, a Class A Automotive HUD Controller Firmware. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Firmware rendering vehicle speed, navigation, and ADAS warnings on a windshield-projected heads-up display.

[Assistant] Content: Safety requirements are not applicable to the AutoHUD Heads-Up Display Controller because the Class A Automotive HUD Controller Firmware cannot contribute to a hazardous situation. The software does not implement risk control measures per Clause 5.2.3. All output is informational and used for Rendering critical driving information on a windshield heads-up display without clinical decision support.


[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 DermaScan AI (skin lesion classifier, Class B):

"All verification for the skin lesion classifier follows IEC 62311-1 requirements."

[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 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 HeartLink (cardiac telemetry system, Class B):

"Software problem resolution follows IEC 62304-6 Clause 9."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-6" which is incorrect. IEC 62304 has no Part 6. 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 InfuSafe Controller (insulin infusion pump controller, Class C):

"Software maintenance is planned. Software maintenance activities are defined. The maintenance plan covers all aspects. Maintenance follows the plan. The InfuSafe Controller maintenance is documented. Maintenance is performed."

[Assistant]
Verdict: FAIL
Note: The documentation section exhibits repetitive structure. Sentences follow the same structure and convey the same meaning. Each paragraph should cover a distinct aspect with varied structure. Content should be consolidated and each sentence should contribute unique, specific information about the InfuSafe Controller.


[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):

"Integration tests verify that components of the CaloriePal interact correctly at each interface point."

[Assistant]
Verdict: FAIL
Note: Content mandates integration testing 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-DATA-002: "data integrity validation" (Category: data)
Project: CleanRoom Particle Counter Logger | Cleanroom Environmental Logger | Class A
Logging and displaying airborne particle counts for cleanroom compliance. Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring 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: Data integrity of all stored records in the Cleanroom Environmental Logger shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Cleanroom Environmental Logger 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 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 cybersecurity and health IT standards for RespiRate Respiratory Monitor, a Class B Respiratory Rate Monitor Firmware. Reference IEC 62304 Clause 5.1.2.
Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

[Assistant] Content: Security controls for the RespiRate Respiratory Monitor are derived from IEC 81001-5-1:2021, which mandates a security risk management process parallel to the ISO 14971 safety risk process. IEC 82304-1:2016 is applied where the Respiratory Rate Monitor Firmware runs on general-purpose computing platforms outside the manufacturer's direct hardware control.


[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 baseline security requirements for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clause 5.2.2.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: Security requirements for the NeoFeed Neonatal Feeding Pump address authentication, data protection, and access control for the Neonatal Feeding Pump Firmware. All persistent data is encrypted at rest, and data in transit over nurse call uses transport layer encryption. Security requirements are aligned with IEC 81001-5-1:2021.


[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 risk control coverage verification for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Risk control coverage analysis for the InhaleSense Smart Inhaler Tracker per Clause 7.3.2 confirms that every software-implemented risk control has a linked verification result demonstrating its effectiveness. Any risk control without verification evidence is treated as a critical gap blocking release of the Smart Inhaler Adherence Tracker.


[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):

"Formal design reviews with independent reviewers are conducted at each phase gate for the NurseCall Hub. Review findings are tracked to closure."

[Assistant]
Verdict: FAIL
Note: Content mandates formal design reviews with independent reviewers for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent review is required only for Class C.


[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 development follows IEC 62304 Clause 4.5 requirements for user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 4.5 which does not exist. Clause 4 only has 4.1, 4.2, 4.3. The reference must be corrected to a valid clause number.


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

[User]
Write a SAD section on architecture verification scope for AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

[Assistant] Content: This architecture is subject to verification per Clause 5.3.6 before the AIDose Chemotherapy Decision Support proceeds to implementation. Reviewers confirm that the architecture addresses all SRS requirements, interfaces are fully specified, and SOUP items are integrated per Clause 5.3.3.


[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 PillRemind (medication reminder app, Class A):

"An independent safety reviewer shall verify all risk control measures implemented in the PillRemind software before each release."

[Assistant]
Verdict: FAIL
Note: Content mandates independent safety review for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent verification is a Class C requirement, 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 EchoAssist (echocardiogram analysis aid, Class B):

"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 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 MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clauses 9.1, 9.2.
Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

[Assistant] Content: The MedImage PACS Viewer problem reporting process per Clause 9.1 captures all software anomalies with sufficient detail for reproduction and root cause investigation. Clause 9.2 investigation assesses whether the problem represents a safety risk, determines the affected scope within the Web PACS Image Viewer, and identifies the corrective action required.


[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 development methodology for Class B for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clause 5.1.1.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: Development of the PathCloud AI Histology Analyzer proceeds through a V-model lifecycle where each development phase has a paired verification phase. For Class B, the mandatory verification phases are architecture verification, integration testing, and system testing. Detailed design verification is omitted, as Clause 5.4 activities are not required at this classification level.


[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-INTF-001: "data export and interoperability" (Category: interface)
Project: DermaLens Teledermatology Platform | Cloud Teledermatology SaMD | Class B
AI-assisted triage scoring of skin lesion images submitted through a mobile teledermatology workflow. Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

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 DermaLens Teledermatology Platform shall exchange data with external systems via REST API using the specified message format with error handling.
Rationale: Interoperability enables integration of Cloud Teledermatology SaMD data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


[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: "data integrity validation" (Category: data)
Project: PaceSet Pacemaker Programmer | Cardiac Pacemaker Programmer Software | Class C
Programming and interrogating implanted cardiac pacemakers including rate settings, sensitivity, and output parameters. Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

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 integrity of all stored records in the Cardiac Pacemaker Programmer Software shall be verified using CRC or equivalent checksums upon read-back.
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 FMEA section on risk control verification for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: Verification of risk control measures for the AquaGuard Water Quality Monitor follows Clause 7.3.1. Each software-implemented control is tested to demonstrate that the hazardous condition is mitigated to an acceptable level. Verification results per Clause 7.3.3 are documented in the risk management file for the Water Quality Monitoring Firmware.


[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: DoseVerify In-Vivo Dosimetry System | In-Vivo Dosimetry Verification Software | Class C
Real-time verification of delivered radiation dose using in-vivo dosimeter measurements during treatment. Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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 DoseVerify In-Vivo Dosimetry System shall detect corrupted measurement records through integrity checking and flag affected entries for review.
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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-002: "alarm generation and notification" (Category: functional)
Project: GaitSense Walking Analysis | Gait Analysis Insole Firmware | Class B
Quantitative gait analysis using instrumented insoles for orthopedic and rehabilitation assessment. Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

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: Alarm thresholds shall be configurable per clinical protocol. The GaitSense Walking Analysis shall trigger alerts within the maximum allowable latency of a threshold crossing.
Rationale: Timely alarm generation is essential for the Gait Analysis Insole Firmware to alert clinicians to abnormal conditions requiring intervention.
Priority: Mandatory
Acceptance Criterion: Alarm triggers within the specified response time of a threshold crossing, measured over 50 test crossings with no false negatives.
Source: Risk control


[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 PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clauses 8.2, 8.2.1.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Changes to the PharmaSafe CDSS 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SAFE-001: "fail-safe behavior specification" (Category: safety)
Project: BalanceBoard Vestibular Trainer | Balance Training Platform Firmware | Class B
Measuring postural sway and providing visual biofeedback during vestibular rehabilitation. Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

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: A deterministic safe-state transition shall be triggered by any detected critical fault condition in the BalanceBoard Vestibular Trainer, with all active outputs brought to a known safe configuration.
Rationale: A deterministic safe-state transition prevents the Balance Training Platform Firmware from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: Safe state transition completes within the specified time limit for each defined critical fault, verified by fault injection during operation.
Source: Risk control


[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 InfuSafe Controller (insulin infusion pump controller, Class C):

"REQ-SRS-078: The InfuSafe Controller shall maintain data integrity during concurrent access by multiple users. No data corruption or loss shall occur. Acceptance criterion: execute concurrent read/write operations and verify data consistency. Priority: Mandatory. Source: System requirement."

[Assistant]
Verdict: PASS
Note: Content requirement is properly structured with measurable acceptance criteria. 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 PhysioTrack Rehab (rehabilitation tracking system, Class B):

"Problem resolution for the PhysioTrack Rehab follows Clause 9. Problem reports capture severity, affected version, and steps to reproduce (Clause 9.1). Investigation per Clause 9.2 determines root cause. Trends are analyzed per Clause 9.6 at each milestone review."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PhysioTrack Rehab (rehabilitation tracking system, Class B). Standards references are accurate.


[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: OBDView Diagnostic Display | Vehicle Diagnostic Display App | Class A
Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use. Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

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 OBDView Diagnostic Display software shall not implement any function that could directly control a therapeutic output, modify a diagnostic conclusion, or trigger a clinical alert, consistent with its Class A 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 Vehicle Diagnostic Display App.
Source: Regulatory


[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 ArthroNav (surgical navigation system, Class C):

"This Software Development Plan for the ArthroNav is prepared in compliance with IEC 62304:2006+AMD1:2015 and ISO 14971:2019. Usability engineering follows IEC 62366-1:2015+AMD1:2020."

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


[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-PERF-002: "resource utilization limits" (Category: performance)
Project: DermaLens Teledermatology Platform | Cloud Teledermatology SaMD | Class B
AI-assisted triage scoring of skin lesion images submitted through a mobile teledermatology workflow. Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

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 Cloud Teledermatology SaMD shall not exceed the allocated budget, with sufficient margin for stack overflow protection.
Rationale: Memory constraints are fixed by the Azure Kubernetes Service + CDN hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
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 scope boundaries of the software system for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: Scope is limited to the TransVent Transport Ventilator software items developed under this plan and released as a single configuration baseline. Peripherals, test jigs, and cloud infrastructure used during Mechanical ventilation during patient transport in pre-hospital and inter-hospital settings are addressed by separate system-level documentation and are not governed by IEC 62304 Clause 5.1.1 activities described herein.


[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-INTF-001: "external system data exchange" (Category: interface)
Project: FleetTrack GPS Tracking Module | Fleet GPS Tracking Firmware | Class A
Real-time GPS tracking and geofence monitoring of fleet vehicles. Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

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 FleetTrack GPS Tracking Module shall exchange data with external systems via LTE-M cellular using the specified message format with error handling.
Rationale: Interoperability enables integration of Fleet GPS Tracking Firmware data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


[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] Can I cite IEC 62304-1 in my documentation?

[Assistant] No. IEC 62304 is a single-part standard. There is no IEC 62304-1. The correct citation is IEC 62304:2006+AMD1:2015.


[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 risk control coverage verification for InsuPrecise Insulin Pump Controller, a Class C Insulin Pump Controller Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

[Assistant] Content: Coverage analysis for risk controls in the InsuPrecise Insulin Pump Controller per Clause 7.3.2 ensures no software-implemented control lacks verification evidence. The analysis cross-references the risk management file with the traceability matrix and the test results to confirm complete coverage for the Insulin Pump Controller Firmware.


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

[User]
Expand requirement SRS-FUNC-007: "data acquisition from primary sensor" (Category: functional)
Project: NutriView Food Diary | Nutritional Tracking Display App | Class A
Personal food logging and nutritional data visualization. Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

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 NutriView Food Diary software shall acquire primary sensor data at the specified sampling rate and store values in a circular buffer for processing by the Nutritional Tracking Display App signal pipeline.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Nutritional Tracking Display App.
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 risk control requirements traceability 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: The ECGInsight Rhythm Interpreter requirements include risk control measures traced from the ISO 14971 risk analysis per Clause 5.2.3. Each risk control implemented in software is expressed as a verifiable requirement and traced forward to design, implementation, and verification of the ECG Interpretation Service.


[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 InfuSafe Controller (insulin infusion pump controller, 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 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 ThermoGuard (body temperature logger, Class A):

"Software development follows IEC 62304 Clause 5.5.6 requirements for detailed design verification."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.5.6 which does not exist. Clause 5.5 has 5.5.1 through 5.5.5 only. The reference must be corrected to a valid clause number.


[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 development platform and build infrastructure for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clause 5.1.4.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The TrainCert Staff Certification Tracker build environment uses Python/Django on Web application. 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 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):

"Hazard analysis for the ThermoGuard identifies that incorrect display of measurement values could mislead the clinician. Risk control measures include input validation (REQ-SRS-023), display range checking, and a visual indicator when data is stale. Residual risk is acceptable per the risk management plan."

[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 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 StepTrack (wellness pedometer app, Class A):

"Code complexity metrics (cyclomatic complexity, nesting depth) are monitored for all StepTrack units. Units exceeding thresholds require refactoring before unit testing."

[Assistant]
Verdict: FAIL
Note: Content mandates code complexity monitoring and unit testing for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Unit verification (Clause 5.5) and complexity metrics are not mandated for Class A.


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

[User]
Expand requirement SRS-FUNC-003: "measurement data archival" (Category: functional)
Project: PowerTrack UPS Monitor | UPS Monitoring Software | Class A
Logging and displaying UPS status for facility infrastructure monitoring. Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

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 PowerTrack UPS Monitor shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via SNMP.
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 SRS section on purpose of the SRS document for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clause 5.2.1.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: The purpose of this SRS is to establish the complete set of software requirements for the DoseCalc Medication Calculator, providing the basis for design, implementation, and verification of the Medication Dose Calculator App. Requirements are organized by type and traced to their originating system requirement, risk control measure, or stakeholder need per Clause 5.2.1.


[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 GlucoEdge Continuous Glucose Platform, a Class B Hybrid CGM Edge-Cloud Platform. Reference IEC 62304 Clauses 8.2, 8.2.1.
Hybrid system: embedded BLE firmware on a wearable CGM patch streams readings to a phone app, which uploads to cloud for trend analysis and physician dashboard.

[Assistant] Content: No change to the GlucoEdge Continuous Glucose Platform baseline is implemented without an approved change request per Clause 8.2. The approval process evaluates the change's impact on safety, regulatory compliance, and previously verified functionality. Post-implementation verification confirms the change was correctly applied per Clause 8.2.3.


[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 IEC 62304-3 a valid standard reference?

[Assistant] No. IEC 62304 has no Part 3 or any sub-parts. It is a single-part standard.


[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 FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clause 5.2.6.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: Requirements verification for the FactoryTemp Industrial Temperature Monitor 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 Industrial Temperature Monitoring Firmware 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 EchoAssist (echocardiogram analysis aid, Class B):

"The EchoAssist 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 EchoAssist (echocardiogram analysis aid, Class B). Standards references are accurate.


[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-PERF-001: "RAM and storage constraints" (Category: performance)
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 operate within the specified RAM and flash memory budget on the Dual ARM Cortex-R5 (lockstep + checker) platform, including all runtime allocations.
Rationale: Memory constraints are fixed by the Dual ARM Cortex-R5 (lockstep + checker) hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
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 SAD section on data paths and processing pipeline for LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: Data within the LinacControl Beam Delivery System Linear Accelerator Control Software traverses three processing stages: acquisition, analysis, and presentation. Each stage is implemented as an independent software item with typed interfaces per Clause 5.3.2. The architecture ensures data integrity is verifiable at each stage boundary during integration testing.


[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: "record keeping duration" (Category: data)
Project: ChestAI Pulmonary Nodule Detector | AI Pulmonary Nodule Detection SaMD | Class B
Computer-aided detection and measurement of pulmonary nodules on chest CT for radiologist review. Cloud AI SaMD analyzing chest CT scans to detect and measure pulmonary nodules, providing CAD overlay for radiologist review. FDA De Novo pathway.

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 ChestAI Pulmonary Nodule Detector shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the AI Pulmonary Nodule Detection SaMD.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


[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 methodology for Class B for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.1.1.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: Development of the WeightAlert Neonatal Scale proceeds through a V-model lifecycle where each development phase has a paired verification phase. For Class B, the mandatory verification phases are architecture verification, integration testing, and system testing. Detailed design verification is omitted, as Clause 5.4 activities are not required at this classification level.


[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 OxyPure Controller (oxygen concentrator controller, Class C):

"Per IEC 62304, the OxyPure Controller software requirements are documented. Per IEC 62304, all requirements for the OxyPure Controller 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 OxyPure Controller.


[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 scope boundaries of the software system for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: The CogniTest Cognitive Assessment App software boundary includes the application firmware, configuration data, and all SOUP components deployed on iPadOS. Hardware components, operating system kernels supplied by the platform vendor, and remote services accessed via PDF export are excluded from the software lifecycle activities defined here, though their influence on software behavior is addressed in the risk analysis.


[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 BloodBank Manager (blood bank inventory system, Class A):

"Each software unit of the BloodBank Manager shall have corresponding unit test cases with full branch coverage."

[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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on safety classification process and documentation for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 4.3.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: Software safety classification for the TriagePro Emergency Scoring App follows the procedure defined in IEC 62304 Clause 4.3. The classification considers whether the Emergency Department Triage SaMD 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.