[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 development plan references IEC 62304 Clause 5.10 and Clause 9.9 for the RadView DICOM."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.10 and 9.9, neither of which exists. Clause 5 ends at 5.8. Clause 9 has 9.1 through 9.8 only. 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 SDP section on verification strategy for Class B -- integration and system testing for TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clauses 5.6, 5.6.3, 5.7.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

[Assistant] Content: Verification of the TeleRehab Remote Patient Monitor at Class B encompasses integration testing and system testing. Integration tests per Clause 5.6.3 exercise the interfaces between software items defined in the architecture, confirming data integrity across module boundaries. System tests per Clause 5.7.1 validate the Remote Rehabilitation Platform against all requirements in the SRS on Web + iOS.


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

[User]
Expand requirement SRS-FUNC-001: "continuous data sampling from MAX30102 PPG sensor" (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 software shall acquire MAX30102 PPG sensor data at the specified sampling rate and store values in a circular buffer for processing by the Heart Rate Display Firmware signal pipeline.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Passive display of resting heart rate for wellness monitoring.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a TRACE section on purpose and scope of the traceability matrix for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clause 5.7.1.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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


[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 failure mode identification approach for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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


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

[User]
Review this documentation excerpt for the EchoAssist (echocardiogram analysis aid, Class B):

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

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


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

[User]
Write a SRS section on data processing and transformation requirements for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 5.2.2.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: Processing requirements for the AnticoagCalc INR Dose Adjuster Anticoagulation Dosing Support Tool cover data acquisition, filtering, computation, and presentation. Each processing step has specified input ranges, output tolerances, and error conditions. Data integrity is maintained throughout the processing pipeline.


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

[User]
Expand requirement SRS-FUNC-003: "primary sensor data capture and buffering" (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: The MedRef Clinical Reference App shall continuously sample primary sensor data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Clinical Drug Reference App.
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 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 PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clause 5.1.2.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Development of the PharmaSafe CDSS software conforms to IEC 62304:2006+AMD1:2015 for the software lifecycle and ISO 14971:2019 for risk management integration. Quality management activities follow ISO 13485:2016, while usability engineering principles from IEC 62366-1:2015+AMD1:2020 inform the user interface design of the Clinical Decision Support System.


[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 SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clause 5.2.2.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

[Assistant] Content: The SleepScore Apnea Screening Tool Sleep Apnea Screening 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 SDP section on internal SOPs and procedures for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clause 5.1.2.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: Internal procedures governing PostureGuard Desk Monitor development include SOP-010 (Software Development Planning), SOP-011 (Risk Management Planning), SOP-012 (Configuration Management), and SOP-013 (Software Verification Planning). These standard operating procedures are maintained under the company's ISO 13485 quality management system and provide detailed work instructions for each lifecycle activity.


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

[User]
Write a SRS section on system boundaries and external dependencies for ChestAI Pulmonary Nodule Detector, a Class B AI Pulmonary Nodule Detection SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud AI SaMD analyzing chest CT scans to detect and measure pulmonary nodules, providing CAD overlay for radiologist review. FDA De Novo pathway.

[Assistant] Content: System boundaries for the ChestAI Pulmonary Nodule Detector are defined at the software interface level. The AI Pulmonary Nodule Detection SaMD receives input from external sensors and produces output via DICOMweb. Components beyond these interfaces are outside the scope of this SRS and are addressed in system-level documentation.


[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 test plan covers system-level tests only. Each requirement in the SRS maps to one or more system test cases. No unit or integration testing is planned for this Class A wellness pedometer app. Test execution is documented per Clause 5.7.5."

[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 THREAT section on STRIDE mitigations traced to requirements for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clause 5.2.3.
Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

[Assistant] Content: Each STRIDE threat identified for the SurgiPlan 3D Surgical Planner maps to a security control requirement in the SRS per Clause 5.2.3. The 3D Surgical Planning SaMD threat-to-requirement traceability ensures that every identified threat is mitigated by a verifiable software control. Residual threats that cannot be fully mitigated in software are documented in the risk management file.


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

[Assistant] Content: Performance requirements for the BSACalc Body Surface Area Tool specify maximum latencies, throughput rates, and resource consumption limits for the BSA Calculator Web App operating on Web SPA. Latency requirements define the maximum time from input event to output response for each critical processing path during Calculating body surface area for oncology dose determination.


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

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

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


[System] You are 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: "power-on self-test sequence" (Category: functional)
Project: GlucoEdge Continuous Glucose Platform | Hybrid CGM Edge-Cloud Platform | Class B
Continuous glucose monitoring with edge processing on wearable and cloud-based trend analysis for clinician review. Hybrid system: embedded BLE firmware on a wearable CGM patch streams readings to a phone app, which uploads to cloud for trend analysis and physician dashboard.

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 power-on self-test shall validate enzymatic glucose sensor communication, memory integrity, and BLE 5.0 to phone connectivity before the Hybrid CGM Edge-Cloud Platform transitions to its operational state.
Rationale: A power-on self-test confirms hardware and software readiness before the Hybrid CGM Edge-Cloud Platform begins use.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

[User]
Write a SRS section on functional requirements overview for FetalGuard Heart Rate Monitor, a Class B Fetal Heart Rate Monitor Firmware. Reference IEC 62304 Clause 5.2.2.
External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

[Assistant] Content: Functional requirements for the FetalGuard Heart Rate Monitor are derived from the system requirements for Continuous external fetal heart rate monitoring during labor with clinical display and from risk control measures identified in the ISO 14971 analysis. Each requirement specifies a single function of the Fetal Heart Rate Monitor Firmware with measurable acceptance criteria.


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

[User]
Review this documentation excerpt for the PillRemind (medication reminder app, Class A):

"The PillRemind verification strategy addresses only system testing as mandated for Class A software per IEC 62304. Each software requirement has at least one corresponding system test case. No unit or integration testing is specified because Class A software cannot contribute to a hazardous situation."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; risk management content follows ISO 14971 framework. Standards references are accurate.


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

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

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

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


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

[User]
Write a SRS section on safety requirements for Class A -- confirms no safety functions for HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: The HeartView Resting HR Display safety requirement section confirms the absence of safety-critical functions. The Heart Rate Display Firmware operates as a display-only system for Passive display of resting heart rate for wellness monitoring, with no closed-loop control, no clinical alarms, and no automated decision-making. The risk analysis confirms no software failure mode contributes to a hazardous situation.


[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 RetinaScan Pro (diabetic retinopathy screening AI, Class B):

"REQ-SRS-067: The RetinaScan Pro shall enforce role-based access control with at least two privilege levels (operator and administrator). Acceptance criterion: verify that operator accounts cannot access administrator functions. Priority: Mandatory. Source: Regulatory."

[Assistant]
Verdict: PASS
Note: Content requirement is properly structured with measurable acceptance criteria. Standards references are accurate.


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

[User]
Review this documentation excerpt for the HeartLink (cardiac telemetry system, Class B):

"The HeartLink addresses IEC 62304 Clause 5.5.2.1 for detailed design verification and Clause 5.3.7 for data archival."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.5.2.1 and 5.3.7, neither of which exists. IEC 62304 has no four-level numbering. Clause 5.3 has 5.3.1 through 5.3.6 only. 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 GlucoEdge Continuous Glucose Platform, a Class B Hybrid CGM Edge-Cloud Platform. Reference IEC 62304 Clause 5.7.1.
Hybrid system: embedded BLE firmware on a wearable CGM patch streams readings to a phone app, which uploads to cloud for trend analysis and physician dashboard.

[Assistant] Content: The purpose of this traceability matrix is to confirm complete coverage of the GlucoEdge Continuous Glucose Platform software requirements through design and verification per Clause 5.7.1. Bidirectional tracing enables identification of gaps (unimplemented requirements) and orphans (implementations without requirements) in the Hybrid CGM Edge-Cloud Platform.


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

[User]
Write a SDP section on problem reporting and investigation for WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clauses 9.1, 9.2.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: The problem resolution process for the WasteTrack Biohazard Logger follows Clauses 9.1 through 9.8. Each problem report is classified by severity, investigated for root cause, and resolved through the change control process. Records are maintained per Clause 9.5, and all resolutions are verified per Clause 9.7 before the Biohazard Waste Tracking App baseline is updated.


[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 CaloriePal (nutrition tracking app, Class A):

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

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


[System] You are an IEC 62304 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):

"Code complexity metrics (cyclomatic complexity, nesting depth) are monitored for all NurseCall Hub 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 a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

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

[Assistant] Content: Computational resource requirements for the RadView DICOM Viewer define the maximum CPU utilization, RAM consumption, and flash/disk usage permitted on Windows/macOS/Linux desktop. The Medical Image Viewer must meet all functional and timing requirements within these resource envelopes.


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

"Each HydroLog module undergoes unit testing followed by integration testing. System testing validates end-to-end behavior. All results are independently reviewed."

[Assistant]
Verdict: FAIL
Note: Content mandates unit testing, integration testing, and independent review for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Clauses 5.5, 5.6, and independent review are not required for Class A.


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

[User]
Write a SDP section on change control process for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: Change control for the NeoFeed Neonatal Feeding Pump Neonatal Feeding Pump Firmware follows Clause 8.2. Each change request is assessed for safety impact, assigned a priority, and tracked to closure. Changes to safety-related requirements or risk control measures require re-evaluation of the ISO 14971 risk analysis before implementation.


[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: "data processing timing constraint" (Category: performance)
Project: AutoHUD Heads-Up Display Controller | Automotive HUD Controller Firmware | Class A
Rendering critical driving information on a windshield heads-up display. Firmware rendering vehicle speed, navigation, and ADAS warnings on a windshield-projected heads-up 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 AutoHUD Heads-Up Display Controller shall process acquired data and update the output within the specified end-to-end latency from sample acquisition to display update.
Rationale: Bounded processing latency ensures the Automotive HUD Controller Firmware provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


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

[User]
Write a FMEA section on failure mode identification approach for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

[Assistant] Content: Failure modes for each TempWatch Body Temperature Logger software function are identified by systematic analysis of data flow paths, processing algorithms, and interface transactions. For each function, the analysis considers: incorrect output, missing output, output at wrong time, and unexpected output. Causes include coding defects, resource exhaustion, race conditions, and corrupted input from MAX30208 temperature sensor.


[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: "RAM and storage constraints" (Category: performance)
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: Peak memory consumption of the Chemotherapy Infusion Pump Firmware shall not exceed the allocated budget, with sufficient margin for stack overflow protection.
Rationale: Exceeding memory limits could cause undefined behavior in the Chemotherapy Infusion Pump Firmware, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

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

"In accordance with ISO 14971:2020, verification activities include system testing."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971:2020" which is incorrect. No 2020 edition. Current: ISO 14971:2019. All references must be corrected.


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

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

"Architectural design follows ISO 14971-2 Clause 5.3 for Class C devices."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971-2" which is incorrect. ISO 14971 has no Part 2. ISO/TR 24971:2020 is a separate technical report. 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 SAD section on error propagation and data integrity in the pipeline for NeoVent Neonatal Ventilator, a Class C Neonatal Ventilator Firmware. Reference IEC 62304 Clause 5.3.2.
Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

[Assistant] Content: Data integrity in the NeoVent Neonatal Ventilator pipeline is maintained through validation at every software item boundary. The architecture specifies error codes, timeout behavior, and recovery actions for each interface. The Neonatal Ventilator Firmware logs all data integrity failures for post-deployment analysis.


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

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

"The lifecycle processes for the VentAssist Pro comply with IEC 62304-2."

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


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

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

"The NurseCall Hub integration plan defines incremental integration of all software units with interface testing at each step per Clause 5.6."

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


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

[User]
Expand requirement SRS-FUNC-001: "micro-flow sensor data capture and buffering" (Category: functional)
Project: InsuPrecise Insulin Pump Controller | Insulin Pump Controller Firmware | Class C
Automated insulin delivery control with programmable basal rates and bolus calculations. Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

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 InsuPrecise Insulin Pump Controller software shall acquire micro-flow sensor data at the specified sampling rate and store values in a circular buffer for processing by the Insulin Pump Controller Firmware signal pipeline.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Insulin Pump Controller Firmware.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a SDP section on change control process for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: No change to the BrachyDose HDR Afterloader Controller 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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the PillRemind (medication reminder app, Class A):

"Software changes to the PillRemind are evaluated for risk impact per Clause 7.4. Each change request includes a risk assessment determining whether new hazards are introduced or existing risk controls are affected. Re-verification of affected risk controls is required before release."

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


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

[User]
Write a SDP section on milestones and phase transition criteria for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 5.1.1.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: Milestones governing the CardioCloud ECG Analysis Service 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 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 ChemoCalc (chemotherapy dose calculator, Class C):

"Software problem resolution follows ISO 14971-1 Clause 9."

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for PulmoCheck Spirometry Analyzer, a Class B Spirometry Analysis Software. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

[Assistant] Content: Requirements in this SRS are identified using the format SRS-PUL-NNN, where NNN is a sequential number. Each requirement states a single testable capability per Clause 5.2.2 and is classified as functional, performance, interface, or safety. Derived requirements that do not trace to a system requirement are flagged for separate review.


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

"MC/DC coverage of 80% is required for all safety-critical modules of the ThermoGuard."

[Assistant]
Verdict: FAIL
Note: Content mandates code coverage targets for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Coverage targets are Class B/C considerations. Class A has no coverage requirements.


[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 HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clause 5.2.3.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: Software-implemented risk controls for the HeartView Resting HR Display are documented as explicit requirements per Clause 5.2.3. Traceability from the ISO 14971 risk analysis through the SRS to verification test cases ensures that every risk control measure is implemented and verified in the Heart Rate Display 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 RadView DICOM (DICOM image viewer, Class A):

"The RadView DICOM integration testing approach uses bottom-up integration with stub drivers replaced incrementally as real components become available."

[Assistant]
Verdict: FAIL
Note: Content mandates bottom-up 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 compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"The HydroLog 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 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):

"All interface points between LabView Portal modules are covered by integration test cases."

[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 SAD section on architecture verification scope for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: The architecture described in this document is verified per Clause 5.3.6, confirming that all software requirements are addressed by at least one software item. Verification also confirms that the GlucoSpot Continuous Glucose Display CGM Display App architecture supports the defined interfaces and does not introduce new hazards.


[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 CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clause 5.2.3.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

[Assistant] Content: Clause 5.2.3 requires that risk control measures implemented in the CleanRoom Particle Counter Logger software appear as traceable requirements. The traceability chain runs from the ISO 14971 hazard analysis to the SRS requirement to the test case verifying the control's effectiveness in the Cleanroom Environmental Logger.


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

[User]
Expand requirement SRS-SEC-002: "authentication for configuration access" (Category: security)
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: The SupplyChain Procurement Portal shall require authentication before allowing modification of device configuration parameters via REST API.
Rationale: Access control prevents unauthorized modification of the Supply Chain Procurement System operating parameters.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


[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 cybersecurity and health IT standards for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clause 5.1.2.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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


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

"Detailed design documentation per Clause 5.4 is produced for every software unit of the NurseCall Hub."

[Assistant]
Verdict: FAIL
Note: Content mandates detailed design documentation for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Detailed design (Clause 5.4) is required only for Class C.


[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 WoundTrack Healing Analyzer, a Class B Wound Assessment App. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

[Assistant] Content: Documentation of WoundTrack Healing Analyzer 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 Wound Assessment App during Photographic wound measurement and healing progress tracking for clinical review, severity and probability ratings, and references to applicable risk control measures.


[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: "data acquisition from pH electrode" (Category: functional)
Project: AquaGuard Water Quality Monitor | Water Quality Monitoring Firmware | Class A
In-situ measurement of water quality parameters for environmental monitoring. Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

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 AquaGuard Water Quality Monitor software shall acquire pH electrode data at the specified sampling rate and store values in a circular buffer for processing by the Water Quality Monitoring Firmware signal pipeline.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Water Quality Monitoring Firmware.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a SDP section on tool qualification for Class B and C for RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clause 5.1.4.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

[Assistant] Content: Verification tools for the RenalDose Renal Adjustment Calculator Renal Dose Adjustment Calculator are qualified per Clause 5.1.4. Qualification records document the tool name, version, intended use in the verification process, and evidence that the tool produces correct results. Tools whose output is not relied upon for verification decisions do not require qualification.


[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 VentAssist Pro (ICU ventilator controller, Class C):

"Software problem resolution follows IEC 14971 Clause 9."

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


[System] You are a 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: "memory usage budget" (Category: performance)
Project: SurgiPlan 3D Surgical Planner | 3D Surgical Planning SaMD | Class B
Preoperative 3D planning of joint replacement procedures with implant sizing and alignment. Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

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

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


[System] You are 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 data paths and processing pipeline for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.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 data flow begins at the load cell with 24-bit ADC interface and terminates at the user-facing output. Intermediate processing stages -- including validation, filtering, and computation -- are implemented as separate software items with defined interfaces per Clause 5.3.2. The Neonatal Scale Firmware data flow is documented to support traceability and integration testing.


[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 problem reporting and investigation for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

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


[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 Class B development lifecycle includes requirements analysis (Clause 5.2), architectural design (Clause 5.3), implementation, and multi-level verification. Integration testing per Clause 5.6 validates component interactions. System testing per Clause 5.7 verifies end-to-end functionality."

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


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

[User]
Write a SDP section on problem reporting and investigation for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clauses 9.1, 9.2.
Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

[Assistant] Content: Software problems discovered during DermaAssist Skin Lesion Classifier development are documented as problem reports per Clause 9.1, including a description of the anomaly, steps to reproduce, and the affected configuration item. Investigation per Clause 9.2 determines the root cause, assesses the impact on previously verified items, and identifies whether the problem affects the safety or effectiveness of the Skin Lesion Classification App.


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

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

"The lifecycle processes for the SleepWell comply with IEC 14971."

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


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

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

[Assistant] Content: Verification of NeuroTune DBS Programmer software requirements follows Clause 5.2.6. Reviewers confirm that every requirement is complete, consistent, testable, and traceable. Requirements that implement risk controls are additionally verified against the ISO 14971 risk management file for the Deep Brain Stimulator Programmer App.


[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 VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clause 5.2.1.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

[Assistant] Content: The system description for the VitalPulse SpO2 Monitor threat model identifies all assets requiring protection: patient data, device configuration, firmware integrity, and the availability of the Pulse Oximeter Firmware for Continuous monitoring of blood oxygen saturation and pulse rate with clinical alarms. Trust boundaries are drawn at each external interface: I2C, UART to display.


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

[User]
Write a SDP section on requirements elicitation and documentation for AutoPancreas Closed-Loop Glucose Controller, a Class C Artificial Pancreas Controller Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

[Assistant] Content: The AutoPancreas Closed-Loop Glucose Controller software requirements are captured in the SRS per Clause 5.2.1. Sources include system requirements for the Artificial Pancreas Controller Firmware, risk control measures from the ISO 14971 analysis, and regulatory requirements from the target markets. Each requirement is verifiable and traceable.


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

"The ThermoGuard employs Test-Driven Development with unit tests written before implementation."

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


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

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

"Each MedInventory module shall have a traceability matrix linking detailed design elements to unit test cases with full coverage."

[Assistant]
Verdict: FAIL
Note: Content mandates detailed design traceability to unit tests for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Detailed design (Clause 5.4) and unit verification (Clause 5.5) are not required for Class A.


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

[User]
Write a SRS section on system boundaries and external dependencies for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clause 5.2.2.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: The MedRef Clinical Reference App system overview identifies all external entities interacting with the Clinical Drug Reference App: input sources (external data), output destinations (offline SQLite cache), and the iOS/Android native execution environment. Requirements for each external interface are documented in the interface requirements section.


[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 SOUP risk evaluation and anomaly management for SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

[Assistant] Content: SOUP anomaly evaluation for the SleepScore Apnea Screening Tool per Clause 7.1.3 reviews published defect lists for each third-party component. Anomalies that could affect the Sleep Apnea Screening App safety or functionality are documented in the risk management file with corresponding risk control measures.


[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 external interface architecture for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.3.2.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The HemaCount Digital Cell Counter uses adapter patterns for all external interfaces: USB camera, LIS HL7v2 integration, desktop GUI. Each adapter implements a common internal interface per Clause 5.3.2, isolating the IVD Digital Cell Counter Software processing logic from external protocol details.


[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 sensor and communication protocol requirements for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clause 5.2.2.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: The WaveReview EEG Archive Viewer communication interfaces include EDF/EDF+ file format, desktop GUI connecting the EEG Archive Viewer to external systems and sensors. Each interface requirement specifies the expected behavior under normal operation and the response to communication failure conditions.


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

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

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

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


[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 problem reporting and investigation for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

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


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

[User]
Expand requirement SRS-FUNC-006: "continuous data sampling from fundus camera DICOM input" (Category: functional)
Project: RetinaScan Diabetic Retinopathy Screener | Retinal Screening Software | Class B
AI-assisted screening of retinal images for diabetic retinopathy signs, requiring specialist confirmation. Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist review.

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

[Assistant]
Description: The RetinaScan Diabetic Retinopathy Screener software shall acquire fundus camera DICOM input data at the specified sampling rate and store values in a circular buffer for processing by the Retinal Screening Software signal pipeline.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for AI-assisted screening of retinal images for diabetic retinopathy signs, requiring specialist confirmation.
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 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-001: "VEML6075 UV sensor data capture and buffering" (Category: functional)
Project: SunGuard UV Index Display | UV Exposure Display Firmware | Class A
Passive display of UV index for personal awareness. Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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

[Assistant]
Description: The SunGuard UV Index Display shall continuously sample VEML6075 UV sensor 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 Passive display of UV index for personal awareness.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

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

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

[Assistant]
Description: The GlucoSpot Continuous Glucose Display shall maintain measurement accuracy within the specified tolerance across the full operating range of the primary sensor.
Rationale: Measurement accuracy directly affects clinical decisions based on the CGM Display App 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 a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"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 MedInventory 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 MedInventory.


[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 and trend analysis for problems for ECGInsight Rhythm Interpreter, a Class B ECG Interpretation Service. Reference IEC 62304 Clauses 9.4, 9.6.
Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

[Assistant] Content: All ECGInsight Rhythm Interpreter problem corrections enter the change control process per Clause 9.4 before integration into the baseline. Trend analysis per Clause 9.6 tracks defect density, time-to-resolution, and defect category distribution across the ECG Interpretation Service development lifecycle to drive process improvement.


[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 RadView DICOM (DICOM image viewer, Class A):

"For the Class A RadView DICOM, verification is limited to system-level test execution per Clause 5.7. The developer performs verification. No independent review is required. Test records include pass/fail results and defect references."

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


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

[User]
Expand requirement SRS-SAFE-001: "absence of safety-critical functions" (Category: safety)
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: No software path in the MedRef Clinical Reference App shall control therapeutic outputs, modify diagnostic results, or generate clinical alerts, confirming the validity of the Class A safety classification.
Rationale: The Class A classification of the Clinical Drug Reference App depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Code review confirms no software path exists that controls therapeutic outputs, modifies diagnostic results, or generates clinical alerts.
Source: Regulatory


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

[User]
Write a SRS section on data format and interoperability requirements 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: The CardioRhythm ECG Analyzer data format requirements ensure interoperability with external systems connected via SPI, BLE 5.0. Data structures, encoding schemes, and byte ordering are fully specified. The Single-Lead ECG Device Firmware handles version mismatches in data formats gracefully.


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

[User]
Review this documentation excerpt for the BloodBank Manager (blood bank inventory system, Class A):

"The BloodBank Manager addresses IEC 62304 Clause 5.5.6 (detailed design verification) through formal review."

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


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

[User]
Review this documentation excerpt for the WoundTrack (wound measurement imaging system, Class B):

"The WoundTrack addresses IEC 62304 Clause Annex B.3 for detailed design verification and Clause 7.5 for data archival."

[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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"Code reviews by personnel independent of the development team are mandatory for all changes."

[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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SEC-002: "data-at-rest encryption" (Category: security)
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 encrypt patient-identifiable data at rest, ensuring that raw storage access cannot reveal protected health information.
Rationale: Encryption of stored patient data protects against unauthorized disclosure if the Neonatal Ventilator Firmware storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


[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 traceability scope including risk controls for SeismicWatch Earthquake Early Warning, a Class A Seismic Early Warning Firmware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Firmware for a network of MEMS accelerometers providing earthquake early warning by detecting P-waves and estimating magnitude.

[Assistant] Content: The SeismicWatch Earthquake Early Warning traceability matrix extends beyond functional requirements to include risk control traceability per Clause 7.3.2. Each risk control measure implemented in the Seismic Early Warning Firmware software is traced from the ISO 14971 hazard through the software requirement to the verification test confirming its effectiveness.


[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 functional requirements overview for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 5.2.2.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: Functional requirements for the DoseLog Radiation Badge Reader are derived from the system requirements for Reading and archiving personal radiation exposure data from dosimeter badges and from risk control measures identified in the ISO 14971 analysis. Each requirement specifies a single function of the Dosimetry Data Logger with measurable acceptance criteria.


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

[User]
Write a SRS section on system boundaries and external dependencies for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: External dependencies of the BrachyDose HDR Afterloader Controller include the Dual redundant PLC operating environment, source position encoder, and stepper motor driver. The HDR Brachytherapy Afterloader Firmware requirements assume these dependencies operate within their specified parameters; failure modes of external components are addressed in the risk analysis.


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

[User]
Review this documentation excerpt for the PillRemind (medication reminder app, Class A):

"Each PillRemind unit undergoes boundary value analysis, equivalence class partitioning, and error guessing as part of unit verification per Clause 5.5."

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


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

[User]
Write a SRS section on sensor and communication protocol requirements for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.2.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: Interface requirements for the AirSentry Urban Air Quality Station specify the communication protocols, data formats, and timing constraints for each external interface of the Air Quality Monitoring Station Firmware. The primary data acquisition interface uses 4G LTE with specified data rates and error detection mechanisms.


[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 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: Company-internal standard operating procedures supplement the international standards for the AirSentry Urban Air Quality Station project. SOP-010 through SOP-013 address development planning, risk management, configuration management, and verification planning. All SOPs are part of the ISO 13485 quality management system and are binding on the Air Quality Monitoring Station Firmware development team.


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

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

"Configuration management follows industry best practices. All items are controlled as appropriate for the AutoDose TPN development effort."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "best practices" provide no project-specific information about the AutoDose TPN total parenteral nutrition calculator. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Write a SDP section on requirements verification approach for DreamLog Sleep Monitor, a Class A Sleep Tracking Display App. Reference IEC 62304 Clause 5.2.6.
Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

[Assistant] Content: Verification of DreamLog Sleep Monitor software requirements follows Clause 5.2.6. Reviewers confirm that every requirement is complete, consistent, testable, and traceable. Requirements that implement risk controls are additionally verified against the ISO 14971 risk management file for the Sleep Tracking Display App.


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

[User]
Expand requirement SRS-FUNC-006: "initialization integrity checks" (Category: functional)
Project: RespiRate Respiratory Monitor | Respiratory Rate Monitor Firmware | Class B
Continuous respiratory rate monitoring with alarm generation for abnormal rates. Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

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

[Assistant]
Description: The RespiRate Respiratory Monitor startup sequence shall include diagnostic checks of all critical subsystems and report any detected faults before allowing operational use.
Rationale: Startup verification prevents the Respiratory Rate Monitor Firmware from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

[User]
Expand requirement SRS-SAFE-001: "fault response and safe shutdown" (Category: safety)
Project: PressoTrack Blood Pressure Trending | Ambulatory Blood Pressure Monitor Firmware | Class B
Automated periodic blood pressure measurement and trending over 24 hours. Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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 PressoTrack Blood Pressure Trending, with all active outputs brought to a known safe configuration.
Rationale: A deterministic safe-state transition prevents the Ambulatory Blood Pressure Monitor Firmware from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: Safe state transition completes within the specified time limit for each defined critical fault, verified by fault injection during operation.
Source: Risk control


[System] You are a regulatory 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 SupplyChain Procurement Portal, a Class A Supply Chain Procurement System. Reference IEC 62304 Clauses 8.1, 8.1.1.
Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

[Assistant] Content: Configuration items for the SupplyChain Procurement Portal include source code, build scripts, the SDP itself, software requirements, and verification records. Each item is uniquely identified by its path in the version control repository and its revision identifier, ensuring that any configuration baseline can be precisely reproduced as required by IEC 62304 Clause 8.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 data processing and transformation requirements for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clause 5.2.2.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: Data processing requirements for the NeuroTune DBS Programmer define the transformations applied to raw input from NFC/BLE telemetry to produce the output presented to the user. Each transformation has defined accuracy bounds and error handling behavior specific to the Deep Brain Stimulator Programmer App operational context.


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

[User]
Write a SAD section on architecture verification scope for RetinaScan Diabetic Retinopathy Screener, a Class B Retinal Screening Software. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist review.

[Assistant] Content: The architecture described in this document is verified per Clause 5.3.6, confirming that all software requirements are addressed by at least one software item. Verification also confirms that the RetinaScan Diabetic Retinopathy Screener Retinal Screening Software architecture supports the defined interfaces and does not introduce new hazards.