[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 AutoDose TPN (total parenteral nutrition calculator, Class C):

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

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


[System] You are a regulatory 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):

"All deliverables undergo review by an independent technical reviewer not involved in development."

[Assistant]
Verdict: FAIL
Note: Content mandates independent review for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent review is required only for Class C (Clause 5.5.4, 5.7.4).


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

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

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


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

[User]
Expand requirement SRS-FUNC-003: "audit trail and data export" (Category: functional)
Project: SurgLog Procedure Documentation App | Surgical Documentation App | Class A
Documentation and review of surgical procedure notes. Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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 SurgLog Procedure Documentation App shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via REST API.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Surgical Documentation App.
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 InfuSafe Controller (insulin infusion pump controller, Class C):

"The InfuSafe Controller software development conforms to IEC 62304:2015, with risk management per ISO 14971:2019."

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


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

[User]
Expand requirement SRS-INTF-002: "data export and interoperability" (Category: interface)
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: The Chemotherapy Infusion Pump Firmware shall support bidirectional data exchange with external systems over stepper motor driver.
Rationale: External system connectivity is required for the Chemotherapy Infusion Pump 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 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-005: "measurement data archival" (Category: functional)
Project: MindCalm Meditation Timer | Meditation Wellness App | Class A
Guided meditation timing with optional passive biometric display. Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

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 MindCalm Meditation Timer shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via HealthKit/Google Fit API.
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 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 InfuSafe Controller (insulin infusion pump controller, Class C):

"The maintenance plan ensures continued compliance with applicable requirements. Updates are managed through established change control as appropriate."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "applicable requirements" provide no project-specific information about the InfuSafe Controller insulin infusion pump controller. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Write a SRS section on external system communication requirements for PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clause 5.2.2.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

[Assistant] Content: Requirements for external system integration with the PedDose Pediatric Dosing App specify the API contracts, data formats, and error handling behavior for all outbound communication from the Pediatric Dosing Calculator App. The software must handle connection timeouts, malformed responses, and authentication failures without affecting safety-relevant functions.


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

"The StepTrack addresses IEC 62304 Clause Annex B.3 for detailed design verification and Clause 7.5 for performance benchmarking."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex B.3 and 7.5, neither of which exists. IEC 62304 annexes are not cited as requirements. Clause 7 ends at 7.4. 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 ThermoGuard (body temperature logger, Class A):

"Software safety classification is performed per IEC 62311-1 Clause 4.3."

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

[User]
Write a SRS section on latency and throughput requirements for DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: Timing requirements for the DialyFlow Dialysis Fluid Controller include end-to-end latency from sensor acquisition to display update, processing throughput for sustained data streams, and startup time. Each timing requirement has a specific numeric bound and is verified through system testing of the Hemodialysis Fluid Controller Firmware.


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

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

"The development plan references IEC 62304 Clause 5.9 and Clause 5.3.7 for the LabView Portal."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.9 and 5.3.7, neither of which exists. Clause 5 ends at 5.8. Clause 5.3 has 5.3.1 through 5.3.6 only. All clause references must be corrected.


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

[User]
Write a SDP section on change control process for ConveyorGuard Safety Interlock System, a Class A Conveyor Safety Interlock Software. Reference IEC 62304 Clauses 8.2, 8.2.1.
Safety PLC program monitoring conveyor belt guard positions, emergency stops, and light curtains. Functional safety application.

[Assistant] Content: No change to the ConveyorGuard Safety Interlock System 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 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 AnesBot Automated Anesthesia Controller, a Class C Automated Anesthesia Delivery Software. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

[Assistant] Content: Traceability scope for the AnesBot Automated Anesthesia Controller includes both functional requirements and risk control measures. Risk control traceability per Clause 7.3.2 links each hazard cause to the software control, the SRS requirement, the implementation, and the verification evidence for the Automated Anesthesia Delivery Software.


[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 internal SOPs and procedures for MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clause 5.1.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 development team follows company SOPs aligned with ISO 13485:2016 quality management requirements: SOP-010 governs software planning, SOP-012 governs configuration management, and SOP-013 governs verification. Each SOP is version-controlled and reviewed annually to maintain compliance.


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

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

[Assistant] Content: Each risk control for the AirSentry Urban Air Quality Station per Clause 7.2.1 specifies the hazard addressed, the control mechanism, and the verification method. Controls implemented in software per Clause 7.2.2 are traced through the requirements-design-test chain to ensure complete implementation and verification in the Air Quality Monitoring Station Firmware.


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

[User]
Write a SRS section on requirements conventions and identification scheme for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: The PaceSet Pacemaker Programmer SRS follows a structured format: each requirement has a unique ID, a type classification, a priority, a rationale, and acceptance criteria per Clause 5.2.2. Requirements implementing risk control measures per Clause 5.2.3 are explicitly marked to ensure they receive verification attention proportional to their safety significance.


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

"Formal design reviews with independent reviewers are conducted at each phase gate for the StepTrack. 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-005: "configuration persistence and validation" (Category: functional)
Project: HeartView Resting HR Display | Heart Rate Display Firmware | Class A
Passive display of resting heart rate for wellness monitoring. Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

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

[Assistant]
Description: The HeartView Resting HR Display shall allow authorized users to configure operating parameters via I2C and persist settings across power cycles.
Rationale: Configurable parameters allow the Heart Rate Display Firmware 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 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 ArthroNav (surgical navigation system, Class C):

"Compliance with IEC 62304 Clause Annex A.1 (post-market surveillance) and Clause 10.1 (continuous monitoring) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 10.1, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. IEC 62304 has no Clause 10. Standard ends at Clause 9. All clause references must be corrected.


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

[User]
Write a TRACE section on purpose and scope of the traceability matrix for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clause 5.7.1.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: This traceability matrix demonstrates bidirectional traceability between requirements, design elements, and verification activities for the BrachyDose HDR Afterloader Controller per IEC 62304 Clause 5.7.1. Each software requirement is traced forward to the design element that implements it and to the test case that verifies it, ensuring complete coverage with no unlinked requirements or untested design elements.


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

"Code complexity metrics (cyclomatic complexity, nesting depth) are monitored for all ThermoGuard 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-SAFE-001: "fail-safe behavior specification" (Category: safety)
Project: NeoVent Neonatal Ventilator | Neonatal Ventilator Firmware | Class C
Mechanical ventilatory support for neonatal patients with precise low-volume delivery. Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

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 NeoVent Neonatal Ventilator, with all active outputs brought to a known safe configuration.
Rationale: Fail-safe behavior is essential to prevent the Neonatal Ventilator Firmware from causing harm when its software detects an unrecoverable error.
Priority: Mandatory
Acceptance Criterion: All 20 defined fault scenarios result in correct safe-state entry within timing limits across 10 iterations each.
Source: Risk control


[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: SupplyChain Procurement Portal | Supply Chain Procurement System | Class A
Managing procurement of medical supplies with approval tracking. Web portal for ordering medical supplies with approval workflows. Procurement and logistics 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: Data integrity of all stored records in the Supply Chain Procurement System 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: 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 requirements verification approach for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 5.2.6.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: The AnticoagCalc INR Dose Adjuster requirements verification checklist per Clause 5.2.6 confirms: no ambiguous requirements, no untestable requirements, no contradictions between requirements, and complete traceability to system requirements and risk controls. The review is documented with reviewer names, findings, and disposition.


[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: "device configuration management" (Category: functional)
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: The BalanceBoard Vestibular Trainer shall allow authorized users to configure operating parameters via USB and persist settings across power cycles.
Rationale: Parameter flexibility is essential for the Balance Training Platform Firmware to meet varying clinical requirements across deployment sites.
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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-DATA-001: "data retention period" (Category: data)
Project: PulseRing Smart Ring Monitor | Wearable Smart Ring Firmware + Companion App | Class B
Continuous photoplethysmography-based heart rate and SpO2 monitoring via wearable ring with mobile companion. Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

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 PulseRing Smart Ring Monitor 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 Wearable Smart Ring Firmware + Companion App.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Expand requirement SRS-DATA-003: "measurement data lifecycle" (Category: data)
Project: 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: Data retention in the FridgeGuard Temperature Logger shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
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 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):

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

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


[System] You are 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: "data processing timing constraint" (Category: performance)
Project: NeoVent Neonatal Ventilator | Neonatal Ventilator Firmware | Class C
Mechanical ventilatory support for neonatal patients with precise low-volume delivery. Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

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 NeoVent Neonatal Ventilator shall process acquired data and update the output within the specified end-to-end latency from sample acquisition to display update.
Rationale: Real-time performance is critical for the Neonatal Ventilator Firmware to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
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 DialysisGuard (hemodialysis machine controller, Class C):

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

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-1" which is incorrect. IEC 62304 is a single-part standard. The correct citation is IEC 62304:2006+AMD1:2015. All references must be corrected.


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

[User]
Write a SDP section on SOUP identification and management for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 8.1.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: Identification of SOUP for the CogniTest Cognitive Assessment App follows Clause 8.1.2. Each SOUP component record includes title, version, supplier, intended function within the Cognitive Assessment Application, 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. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on risk management integration into the lifecycle for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clauses 7.1, 7.1.1.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: Software risk management activities are integrated throughout the AirSentry Urban Air Quality Station development lifecycle in accordance with IEC 62304 Clause 7 and ISO 14971. Risk analysis begins during requirements analysis, with identified hazards traced through design, implementation, and verification to confirm that all risk control measures are effectively implemented and verified.


[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 NurseCall Hub (patient call system dashboard, Class A):

"Per IEC 62304, software safety classification is performed. Per IEC 62304, the safety class is determined. Per IEC 62304, the safety classification is documented. Per IEC 62304, the NurseCall Hub is classified per IEC 62304."

[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 NurseCall Hub.


[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] Does IEC 62304:2006+AMD1:2015 exist?

[Assistant] Yes. IEC 62304:2006+AMD1:2015 is the current edition of the medical device software lifecycle standard. The base standard was published in 2006, with Amendment 1 in 2015.


[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 PhysioTrack Rehabilitation Monitor, a Class B Physical Therapy Tracking System. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

[Assistant] Content: The PhysioTrack Rehabilitation Monitor traceability matrix extends beyond functional requirements to include risk control traceability per Clause 7.3.2. Each risk control measure implemented in the Physical Therapy Tracking System software is traced from the ISO 14971 hazard through the software requirement to the verification test confirming its effectiveness.


[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: DoseCalc Medication Calculator | Medication Dose Calculator App | Class B
Calculating weight-based medication doses for clinical prescribing support. Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

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

[Assistant]
Description: The DoseCalc Medication Calculator shall exchange data with external systems via manual data entry using the specified message format with error handling.
Rationale: External system connectivity is required for the Medication Dose Calculator App 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-001: "computational accuracy requirement" (Category: performance)
Project: FetalGuard Heart Rate Monitor | Fetal Heart Rate Monitor Firmware | Class B
Continuous external fetal heart rate monitoring during labor with clinical display. External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

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 FetalGuard Heart Rate Monitor shall maintain measurement accuracy within the specified tolerance across the full operating range of the 1 MHz Doppler ultrasound transducer.
Rationale: Inaccurate output from the Fetal Heart Rate Monitor Firmware could lead to incorrect clinical actions, making accuracy a safety-critical requirement.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
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 GlucoTrack CGM (continuous glucose monitor display, Class B):

"The GlucoTrack CGM development team follows appropriate processes and procedures. Training is provided as needed to ensure competency in relevant areas."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed" provide no project-specific information about the GlucoTrack CGM continuous glucose monitor display. 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-INTF-002: "primary sensor interface protocol" (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 Fleet GPS Tracking Firmware sensor interface shall establish and maintain reliable communication with the GNSS module via LTE-M cellular.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Fleet GPS Tracking Firmware output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
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 THREAT section on threat model data flow decomposition for CardioRhythm ECG Analyzer, a Class B Single-Lead ECG Device Firmware. Reference IEC 62304 Clause 5.2.2.
Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay diagnosis.

[Assistant] Content: Data flow decomposition for the CardioRhythm ECG Analyzer threat model identifies all pathways where data crosses trust boundaries in the Single-Lead ECG Device Firmware. Each crossing point -- input from external sensors, output to display systems, and communication with remote services via USB -- is analyzed for security threats.


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

[User]
Write a THREAT section on system description for threat modeling for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.2.1.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: Threat modeling for the BeamPlan Radiation Treatment Planner begins with a system description identifying entry points, data stores, and trust boundaries of the Radiation Treatment Planning Software. The model covers the Linux workstation with GPU execution environment, all DICOM RT import/export, desktop GUI with 3D visualization interfaces, and persistent data stores.


[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 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 security requirements cover confidentiality, integrity, and availability of the QMS Audit Trail Service and its data per IEC 81001-5-1:2021. Requirements specify access control mechanisms, encryption for data at rest and in transit, session management, and audit logging.


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

[Assistant] Content: Data flows through the GaitSense Walking Analysis in a defined pipeline: force-sensitive resistors (FSR array) data is acquired, validated, processed through the algorithm chain, and presented via BLE 5.0. Each data transformation step has defined input and output formats per Clause 5.3.2, forming the basis for integration test cases.


[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 lifecycle processes for the HydroLog comply with IEC 62304-4."

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


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

[User]
Write a TRACE section on risk control coverage verification for PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

[Assistant] Content: Coverage analysis for risk controls in the PainScale Digital Assessment Tool 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 Pain Assessment Tool.


[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 CardioLoop Cardiac Resync Controller, a Class C CRT Optimization Firmware. Reference IEC 62304 Clauses 9.4, 9.6.
Firmware for cardiac resynchronization therapy devices optimizing biventricular pacing based on hemodynamic feedback.

[Assistant] Content: Corrections to the CardioLoop Cardiac Resync Controller 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 CRT Optimization Firmware.


[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 gap identification and coverage analysis for HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clause 5.7.4.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

[Assistant] Content: The gap analysis for the HumidityMap Room Condition Logger identifies any software requirements without linked test cases, design elements without source requirements (orphan implementations), and test cases that do not trace to any requirement (unnecessary tests). All gaps are documented and resolved before the Release Readiness Review to confirm that the Environmental Condition Logger verification is complete per Clause 5.7.4.


[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 AutoDose TPN (total parenteral nutrition calculator, Class C):

"Hazard analysis for the AutoDose TPN 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 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 WoundTrack (wound measurement imaging system, Class B):

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

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


[System] You are 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 ISO 14901 a valid standard?

[Assistant] No. ISO 14901 does not exist as a medical device standard. The standard for medical device risk management is ISO 14971:2019. This is a common hallucination.


[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 HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clause 5.2.3.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

[Assistant] Content: The HomeVent BiPAP Controller 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 BiPAP Device Firmware.


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

[User]
Write a SAD section on interface design between software items for AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clause 5.3.2.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

[Assistant] Content: The AIDose Chemotherapy Decision Support Cloud AI Chemotherapy Dosing SaMD software item interfaces per Clause 5.3.2 are defined using typed data structures with explicit ownership semantics. Each interface specifies the pre-conditions, post-conditions, and error conditions. Interface compatibility is verified through integration testing per Clause 5.6.


[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 PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 8.1.2.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: The PaceSet Pacemaker Programmer SOUP register identifies every third-party component deployed in the Cardiac Pacemaker Programmer Software, including version, source, and functional role. Updates to SOUP items trigger re-evaluation of known anomalies per Clause 7.1.3 and regression testing proportional to the scope of change.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clause 7.1.1.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: This simplified FMEA for the BillingBridge Claims Processor Claims Processing Service addresses Clause 7.1.1 by identifying software items that could contribute to hazardous situations. The analysis concludes that the Class A system has no failure modes leading to patient harm -- all failure effects are limited to degraded or absent informational display.


[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 requirements conventions and identification scheme for FallRisk Inpatient Assessment Tool, a Class B Fall Risk Assessment App. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

[Assistant] Content: The FallRisk Inpatient Assessment Tool SRS follows a structured format: each requirement has a unique ID, a type classification, a priority, a rationale, and acceptance criteria per Clause 5.2.2. Requirements implementing risk control measures per Clause 5.2.3 are explicitly marked to ensure they receive verification attention proportional to their safety significance.


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

[User]
Write a SAD section on SOUP component integration and requirements for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The DoseLog Radiation Badge Reader Dosimetry Data Logger integrates SOUP components per Clause 5.3.3 with specified functional requirements and per Clause 5.3.4 with documented hardware/software prerequisites. Each SOUP item's known anomaly list has been evaluated per Clause 7.1.3 and documented in the risk management file.


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

[User]
Write a SRS section on sensor and communication protocol requirements for RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clause 5.2.2.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

[Assistant] Content: External interface requirements for the RenalDose Renal Adjustment Calculator Renal Dose Adjustment Calculator define the data exchanged across each interface boundary: manual input, lab results API. For each interface, requirements specify the protocol, data format, timing, and error recovery behavior.


[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 primary international standards applicable to development for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.1.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: The software lifecycle for the AirSentry Urban Air Quality Station is executed under IEC 62304:2006+AMD1:2015, with risk management per ISO 14971:2019 integrated at each phase gate. Quality system requirements follow ISO 13485:2016, and usability validation of the Air Quality Monitoring Station Firmware follows IEC 62366-1:2015+AMD1:2020.


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

"The RadView DICOM verification approach includes system testing per Clause 5.7 with test cases documented in the software test plan. The developer may perform verification activities. Independent review is not required for Class A. No integration or unit testing is mandated for this DICOM image viewer."

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


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

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

[Assistant] Content: The IncidentReport Clinical Event Logger build environment uses TypeScript/Vue on Web SPA. 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-002: "BME280 data capture and buffering" (Category: functional)
Project: WeatherNode Microclimate Station | Weather Station Firmware | Class A
Automated measurement and transmission of microclimate weather parameters. Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

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 WeatherNode Microclimate Station shall continuously sample BME280 data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Automated measurement and transmission of microclimate weather parameters.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum 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 SRS section on operational context and user population 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: The HumidityMap Room Condition Logger operates as a Environmental Condition Logger where Monitoring and logging temperature/humidity in hospital storage areas. The software interfaces with SHT31 temp/humidity and communicates via LoRaWAN, MQTT. The operational environment, user population, and regulatory context described here constrain the requirements that follow.


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

"Risk management for the DermaScan AI follows Clause 7. Software items contributing to hazardous situations are identified per Clause 7.1.1. Risk control measures are defined per Clause 7.2.1 and verified per Clause 7.3.1. Traceability is documented per Clause 7.3.2."

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


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

[User]
Write a SRS section on enhanced security for Class B and C for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.2.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: The WeightAlert Neonatal Scale Neonatal Scale Firmware implements security-in-depth: secure boot, runtime integrity monitoring, encrypted communications, and input validation on all external interfaces per IEC 81001-5-1:2021. Security testing covers penetration testing, fuzz testing of SPI, and vulnerability scanning.


[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 internal SOPs and procedures for BSACalc Body Surface Area Tool, a Class B BSA Calculator Web App. Reference IEC 62304 Clause 5.1.2.
Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

[Assistant] Content: The BSACalc Body Surface Area Tool development team follows company SOPs aligned with ISO 13485:2016 quality management requirements: SOP-010 governs software planning, SOP-012 governs configuration management, and SOP-013 governs verification. Each SOP is version-controlled and reviewed annually to maintain compliance.


[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 management integration into the lifecycle for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 7.1, 7.1.1.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: Integration of risk management into the RadOnco Cloud Treatment Planner lifecycle ensures that newly identified hazards during development trigger requirement updates, design changes, and additional verification. The risk management file is a living document updated at each phase gate, with traceability maintained per Clause 7.3.2.


[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 WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clauses 8.2, 8.2.1.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

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


[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 configuration identification approach for PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clauses 8.1, 8.1.1.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

[Assistant] Content: The configuration identification scheme for the PainScale Digital Assessment Tool assigns a unique identifier to every controlled artifact: source code modules, build configurations, documentation deliverables, and verification records. The scheme supports reconstruction of any released baseline of the Pain Assessment Tool per Clause 8.1.1.


[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 FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clause 5.2.1.
Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

[Assistant] Content: The SRS for the FridgeGuard Temperature Logger documents every functional, performance, interface, and safety requirement governing the Cold Chain Temperature Logger. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


[System] You are a regulatory 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 sensor and communication protocol requirements for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clause 5.2.2.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

[Assistant] Content: The BreathEasy Air Quality Display interfaces with SCD41 CO2 sensor via I2C. Interface requirements specify the physical layer, data format, sampling rate, and error handling for each connection. All interface requirements are verifiable through integration or system testing.


[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 ScreenFlow Population Health Screener, a Class A Serverless Population Health Screening SaMD. Reference IEC 62304 Clause 5.2.3.
Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

[Assistant] Content: Risk control measures identified in the ISO 14971 risk management process are traced to specific software requirements per Clause 5.2.3. For the ScreenFlow Population Health Screener, this includes controls addressing input data failure modes, communication integrity on REST API, and data validation.


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

"The PillRemind integration test plan covers all inter-module interfaces per Clause 5.6."

[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 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 independent review process for Class C for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.1.1.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: The BeamPlan Radiation Treatment Planner review process mandates independent technical review for all Class C deliverables. The independent reviewer has competence in C++ (computational) + Python (UI) development and IEC 62304 compliance but is not a member of the Radiation Treatment Planning Software development team. Review records include reviewer qualifications, findings, actions taken, and formal sign-off.


[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: "power-on self-test sequence" (Category: functional)
Project: MedRef Clinical Reference App | Clinical Drug Reference App | Class A
Providing searchable drug information and interaction warnings for clinical reference without making prescribing decisions. Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing 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: Upon power-up, the MedRef Clinical Reference App shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Clinical Drug Reference App from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


[System] You are 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 user interaction requirements for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: Interaction requirements for the AquaGuard Water Quality Monitor specify all user-facing behaviors of the Water Quality Monitoring Firmware: screen layouts, navigation flows, alarm presentation (if applicable), and error messaging. Each interaction requirement includes the trigger condition, the expected system response, and the acceptance criteria for verification.


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

[User]
Write a SRS section on resource constraints and scalability for ConsentView Informed Consent Archive, a Class A Consent Document Viewer. Reference IEC 62304 Clause 5.2.2.
Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

[Assistant] Content: The ConsentView Informed Consent Archive resource constraints are derived from the Web SPA hardware capabilities. Requirements specify headroom margins for memory and processing to ensure the Consent Document Viewer remains stable under sustained operation during Read-only viewing of archived informed consent documents.


[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 AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 5.1.1.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: Milestones governing the AnticoagCalc INR Dose Adjuster 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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on latency and throughput requirements for StepSync Activity Tracker, a Class A Wellness Activity Display App. Reference IEC 62304 Clause 5.2.2.
Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

[Assistant] Content: Timing requirements for the StepSync Activity Tracker include end-to-end latency from sensor acquisition to display update, processing throughput for sustained data streams, and startup time. Each timing requirement has a specific numeric bound and is verified through system testing of the Wellness Activity Display App.


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

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

[Assistant] Content: The DoseCalc Medication Calculator Medication Dose Calculator App implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

[User]
Write a FMEA section on documenting failure modes and their effects for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

[Assistant] Content: Each identified failure mode of the VitalPulse SpO2 Monitor is documented per Clause 7.1.4 with the failure mode description, potential causes, local effects, end effects on the Pulse Oximeter Firmware, severity classification, and existing controls. The documentation supports risk control decision-making per Clause 7.2.1.


[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 hazard identification for the specific device for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: Hazard identification for the RadOnco Cloud Treatment Planner per Clause 7.1.2 considers all software functions that could contribute to patient harm. Identified causes include incorrect sensor data processing, loss of communication on DICOM RT import/export, and failure to detect out-of-range conditions during Cloud-based Monte Carlo dose calculation and treatment plan optimization for radiation oncology.


[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 documenting failure modes and their effects for HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

[Assistant] Content: Documentation of HomeVent BiPAP Controller failure modes follows Clause 7.1.4. Each entry in the FMEA register includes: the software item, the failure mode, the potential cause(s), the effect on the BiPAP Device Firmware during Home bilevel ventilatory support with auto-titrating pressure and leak compensation, severity and probability ratings, and references to applicable risk control measures.


[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: "computational accuracy requirement" (Category: performance)
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: The PaceSet Pacemaker Programmer shall maintain measurement accuracy within the specified tolerance across the full operating range of the RF telemetry wand.
Rationale: Inaccurate output from the Cardiac Pacemaker Programmer Software could lead to incorrect clinical actions, making accuracy a safety-critical requirement.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
Source: Regulatory


[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 FMEA scope for Class A -- simplified analysis for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clause 7.1.1.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

[Assistant] Content: This simplified FMEA for the AssetTrack Equipment Inventory Equipment Inventory System addresses Clause 7.1.1 by identifying software items that could contribute to hazardous situations. The analysis concludes that the Class A system has no failure modes leading to patient harm -- all failure effects are limited to degraded or absent informational display.


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

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

"The CardioPulse Monitor fault tree analysis identifies root causes of potential software failures. Control measures include watchdog timers, redundant calculations, and plausibility checks on sensor data. Each measure is a traceable software requirement verified during system testing."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the CardioPulse Monitor (cardiac rhythm monitor, 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 development platform and build infrastructure for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.1.4.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: The VitalBoard Patient Summary build environment uses TypeScript/Angular on Web SPA. Continuous integration builds execute on every commit, ensuring early detection of compilation errors and regression failures. Toolchain versions are locked to the configuration baseline and recorded in the Software Configuration Management Plan.


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

[User]
Write a SDP section on minimal deliverables list for Class A for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clause 5.1.8.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

[Assistant] Content: Required documentation deliverables for the Class A ClinTrial EDC Platform are: this Software Development Plan, the Software Requirements Specification, the System Test Plan and Report, the Software Release Record, and the Risk Management File summary. Detailed design documentation, unit test reports, and integration test reports are not required for Class A and are not produced.


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

"Software release for the ThermoGuard follows Clause 5.8. Completeness is ensured per Clause 5.8.1, version identification per Clause 5.8.2, and known residual anomalies are documented per Clause 5.8.4 and evaluated per Clause 5.8.5."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the ThermoGuard (body temperature logger, Class A). Standards references are accurate.


[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 development follows ISO 13485-2 for the software lifecycle."

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


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

[User]
Expand requirement SRS-PERF-002: "computational accuracy requirement" (Category: performance)
Project: NeoFeed Neonatal Feeding Pump | Neonatal Feeding Pump Firmware | Class C
Precise enteral feeding delivery for neonatal patients with sub-milliliter accuracy. Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

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: Computational results produced by the NeoFeed Neonatal Feeding Pump shall be accurate to within the specified tolerance, validated against reference calculations.
Rationale: Measurement accuracy directly affects clinical decisions based on the Neonatal Feeding Pump Firmware output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
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 PhysioTrack Rehab (rehabilitation tracking system, Class B):

"ISO 13485-2 Section 5.3 requires all software units to be verified."

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


[System] You are a regulatory 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 WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: Risk control measures in the WeightAlert Neonatal Scale are verified per Clause 7.3.1 through the testing activities appropriate to the safety classification. Traceability per Clause 7.3.2 links each identified hazard to its risk control measure, the software requirement implementing the control, and the test case verifying the control's effectiveness in the Neonatal Scale Firmware.