[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: "configuration persistence and validation" (Category: functional)
Project: LabStream LIS Middleware | Laboratory Information Middleware | Class A
Routing and auto-validating laboratory results between analyzers and the laboratory information system. Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

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: Operating parameters of the Laboratory Information Middleware shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Configurable parameters allow the Laboratory Information Middleware to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

[User]
Write a SDP section on cybersecurity and health IT standards 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: Security controls for the PostureGuard Desk Monitor are derived from IEC 81001-5-1:2021, which mandates a security risk management process parallel to the ISO 14971 safety risk process. IEC 82304-1:2016 is applied where the Posture Wellness Display Software runs on general-purpose computing platforms outside the manufacturer's direct hardware control.


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

[User]
Write a FMEA section on failure mode identification approach for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: The ThermoWatch Core Temperature Monitor failure mode identification per Clause 7.1.2 uses a function-by-function analysis of the Core Temperature Monitor Firmware. Each software function is examined for potential failure modes: omission, commission, early, late, and value errors. Potential causes per Clause 7.1.2 include design defects, SOUP anomalies per Clause 7.1.3, and environmental factors.


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

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

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

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

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

[Assistant] Content: Each requirement for the FetalGuard Heart Rate Monitor is assigned a unique identifier and tagged with its type (functional, performance, interface, or safety) per Clause 5.2.2. Requirements are written in "shall" statements that are individually testable. The requirement set is baselined and controlled under the change management process.


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

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

"Verification for the ThermoGuard body temperature logger follows Clause 5.7 only. System tests exercise the software in its target configuration. Clause 5.5 unit verification and Clause 5.6 integration testing are explicitly excluded for Class A."

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


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

[User]
Expand requirement SRS-INTF-002: "data export and interoperability" (Category: interface)
Project: RetinaStim Visual Prosthesis Controller | Retinal Prosthesis Controller Firmware | Class C
Processing camera input and driving retinal implant electrode stimulation patterns for artificial vision. Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

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

[Assistant]
Description: Data interoperability with clinical information systems shall be provided through RF coil to implant, supporting standard message formats.
Rationale: External system connectivity is required for the Retinal Prosthesis Controller Firmware to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

[User]
Write a SAD section on data paths and processing pipeline for PulseRing Smart Ring Monitor, a Class B Wearable Smart Ring Firmware + Companion App. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

[Assistant] Content: The processing pipeline of the PulseRing Smart Ring Monitor consists of sequential data transformations from raw input through processed output. Interface contracts per Clause 5.3.2 define the data format, timing, and error conditions at each pipeline stage boundary. The Wearable Smart Ring Firmware + Companion App architecture supports both streaming and batch processing modes where 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 RadBeam Planner (radiation therapy planning system, Class C):

"The RadBeam Planner addresses IEC 62304 Clause 5.1.12 for security testing and Clause 5.4.5 for deployment validation."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.1.12 and 5.4.5, neither of which exists. Clause 5.1 has 5.1.1 through 5.1.11 only. Clause 5.4 has 5.4.1 through 5.4.4 only. All clause 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: "real-time performance requirement" (Category: performance)
Project: SurgLog Procedure Documentation App | Surgical Documentation App | Class A
Documentation and review of surgical procedure notes. Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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

[Assistant]
Description: End-to-end latency from tablet microphone data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Bounded processing latency ensures the Surgical Documentation App provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


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

"Each NurseCall Hub 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 a medical device regulatory standards expert with comprehensive knowledge of IEC 62304, ISO 14971, ISO 13485, IEC 62366-1, IEC 82304-1, IEC 81001-5-1, IEC 60601-1 and its sub-parts, and associated regulatory guidance. Provide accurate standards references. Never fabricate clause numbers or standard sub-parts.

[User] What is the deepest clause numbering level in IEC 62304?

[Assistant]
IEC 62304 uses up to three levels of clause numbering:

- Level 1: Clause 5 (Software development process)
- Level 2: Clause 5.1 (Software development planning)
- Level 3: Clause 5.1.1 (Software development plan)

There is no fourth level. References like '5.5.2.1' or '5.1.1.1' are invalid.


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

[User]
Expand requirement SRS-FUNC-003: "configuration persistence and validation" (Category: functional)
Project: RadView DICOM Viewer | Medical Image Viewer | Class A
Read-only display of medical images for reference viewing. Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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: Operating parameters of the Medical Image Viewer shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Parameter flexibility is essential for the Medical Image Viewer to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

[User]
Write a SDP section on requirements elicitation and documentation for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

[Assistant] Content: The BreathEasy Air Quality Display software requirements are captured in the SRS per Clause 5.2.1. Sources include system requirements for the Environmental Air Quality Display, risk control measures from the ISO 14971 analysis, and regulatory requirements from the target markets. Each requirement is verifiable and traceable.


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

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

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


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

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

"Maintenance activities follow ISO 14901 Clause 6."

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


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

[User]
Expand requirement SRS-DATA-002: "measurement record integrity" (Category: data)
Project: ConsentView Informed Consent Archive | Consent Document Viewer | Class A
Read-only viewing of archived informed consent documents. Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

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

[Assistant]
Description: Data integrity of all stored records in the Consent Document Viewer shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Consent Document Viewer are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


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

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

"The RadBeam Planner conforms to IEC 62304:2006+AMD1:2015. Safety classification per Clause 4.3 designates this radiation therapy planning system as Class C. Risk management follows ISO 14971:2019 with guidance from ISO/TR 24971:2020."

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


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

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

[Assistant] Content: The AnticoagCalc INR Dose Adjuster software requirements are captured in the SRS per Clause 5.2.1. Sources include system requirements for the Anticoagulation Dosing Support Tool, 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 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-004: "device configuration management" (Category: functional)
Project: CalibrationTracker Equipment Logger | Calibration Record System | Class A
Tracking calibration schedules and recording calibration results for compliance. Web application tracking calibration dates and results for medical test equipment. Administrative record keeping.

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 CalibrationTracker Equipment Logger shall allow authorized users to configure operating parameters via REST API and persist settings across power cycles.
Rationale: Parameter flexibility is essential for the Calibration Record System to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User] Does IEC 62304-1 exist?

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


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

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

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

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


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

[User]
Expand requirement SRS-SAFE-002: "Class A scope validation" (Category: safety)
Project: RadView DICOM Viewer | Medical Image Viewer | Class A
Read-only display of medical images for reference viewing. Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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 RadView DICOM Viewer 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 Medical Image Viewer depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Medical Image Viewer.
Source: Regulatory


[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 HydroRemind Hydration Tracker, a Class A Hydration Tracking Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

[Assistant] Content: The HydroRemind Hydration Tracker 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 Hydration Tracking Firmware, and identifies the corrective action required.


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

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

"IEC 62304 Clause 11.1 requires the DermaScan AI to implement continuous monitoring."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 11.1 which does not exist. IEC 62304 has no Clause 11. The reference must be corrected to a valid clause number.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 7.1.1.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

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


[System] You are 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 ISO 14901 Clause 9."

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


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

[User]
Expand requirement SRS-PERF-003: "RAM and storage constraints" (Category: performance)
Project: PedDose Pediatric Dosing App | Pediatric Dosing Calculator App | Class B
Weight-based pediatric dose calculations with age-appropriate range checking. Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

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 PedDose Pediatric Dosing App memory footprint on Android shall remain within specified limits under worst-case operational scenarios.
Rationale: Exceeding memory limits could cause undefined behavior in the Pediatric Dosing Calculator App, potentially affecting safety.
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 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: "resource utilization limits" (Category: performance)
Project: HandGrip Strength Dynamometer | Hand Dynamometer Firmware | Class B
Measuring hand grip strength and fatigue patterns for rehabilitation progress tracking. Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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

[Assistant]
Description: The HandGrip Strength Dynamometer shall operate within the specified RAM and flash memory budget on the STM32G4 platform, including all runtime allocations.
Rationale: Memory constraints are fixed by the STM32G4 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 SDP section on lightweight review process for Class A for AuditTrail QMS Event Logger, a Class A QMS Audit Trail Service. Reference IEC 62304 Clause 5.1.1.
Microservice capturing and storing quality management system audit events. Logging and reporting only.

[Assistant] Content: The AuditTrail QMS Event Logger review process is proportionate to the Class A risk level. The project lead reviews each deliverable for technical accuracy, and the quality representative verifies compliance with SOPs. Reviews are documented but do not require independent technical review of the QMS Audit Trail Service verification activities.


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

[User]
Write a SDP section on safety classification process and documentation for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 4.3.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The DoseLog Radiation Badge Reader safety classification is a prerequisite for determining the scope of IEC 62304 lifecycle activities. The classification was performed per Clause 4.3 using hazard analysis inputs from the ISO 14971 risk management process. Changes to the Dosimetry Data Logger intended use or risk profile trigger reclassification.


[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: "alarm threshold management" (Category: functional)
Project: CochleaMap CI Fitting Software | Cochlear Implant Fitting Software | Class C
Programming electrode mapping and stimulation parameters for cochlear implant sound processors. Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

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 CochleaMap CI Fitting Software shall generate audible and visual alarms within the specified response time when a monitored parameter exceeds its configured threshold.
Rationale: Alarm functionality is a safety-critical feature of the Cochlear Implant Fitting Software that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


[System] You are a 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: "configurable alarm limits for monitored parameters" (Category: functional)
Project: ThermoWatch Core Temperature Monitor | Core Temperature Monitor Firmware | Class B
Continuous core body temperature monitoring with trend display and threshold alerts. Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

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

[Assistant]
Description: Alarm thresholds shall be configurable per clinical protocol. The ThermoWatch Core Temperature Monitor shall trigger alerts within the maximum allowable latency of a threshold crossing.
Rationale: Alarm functionality is a safety-critical feature of the Core Temperature Monitor Firmware that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


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

[User]
Write a SRS section on enhanced security for Class B and C for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clause 5.2.2.
Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

[Assistant] Content: Security requirements for the SurgiPlan 3D Surgical Planner at the Class B/C level include cryptographic integrity verification of firmware, mutual TLS for external communications via desktop GUI, input sanitization on all external data paths, and a documented security incident response process.


[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 PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

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


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

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

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


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

[User]
Review this documentation excerpt for the StepTrack (wellness pedometer app, Class A):

"Formal code inspections by independent reviewers are required for all StepTrack source code. Each module shall have unit tests with full branch coverage."

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


[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 test strategy for the SleepWell is limited to system-level verification. All requirements from the SRS are covered by system test cases per Clause 5.7.1. Test failures are managed through the software problem resolution process (Clause 9). Unit and integration testing are out of scope for this Class A sleep quality display app."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. 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 PillRemind (medication reminder app, Class A):

"The test strategy for the PillRemind is limited to system-level verification. All requirements from the SRS are covered by system test cases per Clause 5.7.1. Test failures are managed through the software problem resolution process (Clause 9). Unit and integration testing are out of scope for this Class A medication reminder app."

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


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

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

"The PillRemind development follows IEC 14971 for the software lifecycle."

[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 scope boundaries of the software system for ConsentView Informed Consent Archive, a Class A Consent Document Viewer. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

[Assistant] Content: This plan applies to all software executing within the ConsentView Informed Consent Archive Consent Document Viewer and its supporting build and verification infrastructure. External systems that exchange data with the Consent Document Viewer via REST API are covered only at the interface boundary; their internal implementation is outside the scope of this SDP.


[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: CalibrationTracker Equipment Logger | Calibration Record System | Class A
Tracking calibration schedules and recording calibration results for compliance. Web application tracking calibration dates and results for medical test equipment. Administrative record keeping.

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

[Assistant]
Description: Upon power-up, the CalibrationTracker Equipment Logger shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: A power-on self-test confirms hardware and software readiness before the Calibration Record System 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 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 LabView Portal (read-only lab results viewer, Class A):

"Verification of the LabView Portal consists exclusively of system-level testing per IEC 62304 Clause 5.7. Test cases derive from the software requirements specification and execute against the read-only lab results viewer in its target environment. Unit-level and integration testing are not required for Class A and are not performed."

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


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

[User]
Expand requirement SRS-FUNC-004: "real-time data presentation on DICOM" (Category: functional)
Project: RadView DICOM Viewer | Medical Image Viewer | Class A
Read-only display of medical images for reference viewing. Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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 RadView DICOM Viewer display shall present current readings on DICOM within the specified maximum update latency.
Rationale: Display freshness is critical for the Medical Image Viewer to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


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

[User]
Expand requirement SRS-SEC-001: "access control and authorization" (Category: security)
Project: ChestAI Pulmonary Nodule Detector | AI Pulmonary Nodule Detection SaMD | Class B
Computer-aided detection and measurement of pulmonary nodules on chest CT for radiologist review. Cloud AI SaMD analyzing chest CT scans to detect and measure pulmonary nodules, providing CAD overlay for radiologist review. FDA De Novo pathway.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the ChestAI Pulmonary Nodule Detector, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the AI Pulmonary Nodule Detection SaMD operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

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

"Compliance with IEC 62304 Clause 5.1.12 (data archival) and Clause 5.0 (user acceptance testing) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.1.12 and 5.0, neither of which exists. Clause 5.1 has 5.1.1 through 5.1.11 only. Clause 5 starts at 5.1. All clause 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-SEC-002: "cryptographic data security" (Category: security)
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: Patient-identifiable data stored by the RetinaScan Diabetic Retinopathy Screener shall be encrypted at rest using a validated cryptographic algorithm with a key length of at least 256 bits.
Rationale: Encryption of stored patient data protects against unauthorized disclosure if the Retinal Screening Software storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Cryptographic implementation validated against NIST standards with no known vulnerabilities in the selected algorithm.
Source: Regulatory


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

[User]
Write a SRS section on operational context and user population for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.2.2.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: This section describes the operational context of the TriagePro Emergency Scoring App Emergency Department Triage SaMD. The system is intended for Guiding emergency department triage scoring using the Manchester Triage System protocol, operating on iPad web app (PWA). Key interfaces include HL7 FHIR to hospital EMR, tablet touchscreen, barcode scanner. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


[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 SleepWell integration test suite validates all APIs, shared memory interfaces, and IPC mechanisms between software items."

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


[System] You are 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 ChemoFlow Infusion Controller, a Class C Chemotherapy Infusion Pump Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

[Assistant] Content: This section specifies the functional behavior of the ChemoFlow Infusion Controller Chemotherapy Infusion Pump Firmware. Requirements cover data input from drop counting sensor, processing algorithms, output generation via stepper motor driver, and user interaction patterns. All functional requirements are derived from the system specification or 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 RetinaScan Pro (diabetic retinopathy screening AI, Class B):

"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 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 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 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: BalanceBoard Vestibular Trainer | Balance Training Platform Firmware | Class B
Measuring postural sway and providing visual biofeedback during vestibular rehabilitation. Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

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

[Assistant]
Description: A power-on self-test shall validate 4x load cells communication, memory integrity, and USB connectivity before the Balance Training Platform Firmware transitions to its operational state.
Rationale: A power-on self-test confirms hardware and software readiness before the Balance Training Platform Firmware begins use.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[User]
Write a TRACE section on risk control coverage verification for SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

[Assistant] Content: Risk control coverage analysis for the SleepScore Apnea Screening Tool per Clause 7.3.2 confirms that every software-implemented risk control has a linked verification result demonstrating its effectiveness. Any risk control without verification evidence is treated as a critical gap blocking release of the Sleep Apnea Screening 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 PhysioTrack Rehab (rehabilitation tracking system, Class B):

"The PhysioTrack Rehab addresses IEC 62304 Clause 4.4 for performance benchmarking and Clause 9.9 for post-market surveillance."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 4.4 and 9.9, neither of which exists. Clause 4 only has 4.1, 4.2, 4.3. Clause 9 has 9.1 through 9.8 only. All clause references must be corrected.


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

[User]
Write a SRS section on enhanced security for Class B and C for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clause 5.2.2.
Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

[Assistant] Content: The DermaAssist Skin Lesion Classifier Skin Lesion Classification App implements security-in-depth: secure boot, runtime integrity monitoring, encrypted communications, and input validation on all external interfaces per IEC 81001-5-1:2021. Security testing covers penetration testing, fuzz testing of camera API, and vulnerability scanning.


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

[User]
Expand requirement SRS-SAFE-001: "safety classification confirmation for Class A" (Category: safety)
Project: DoseLog Radiation Badge Reader | Dosimetry Data Logger | Class A
Reading and archiving personal radiation exposure data from dosimeter badges. Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

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

[Assistant]
Description: The DoseLog Radiation Badge Reader software shall not implement any function that could directly control a therapeutic output, modify a diagnostic conclusion, or trigger a clinical alert, consistent with its Class A classification.
Rationale: The Class A classification of the Dosimetry Data Logger depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Dosimetry Data Logger.
Source: Regulatory


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

[User]
Write a SDP section on development methodology for Class B for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clause 5.1.1.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: The lifecycle model for the GlucoSpot Continuous Glucose Display combines iterative development with V-model verification gates required by the Class B classification. Architectural design (Clause 5.3) is formally reviewed, integration testing (Clause 5.6) validates inter-module interactions, and system testing (Clause 5.7) confirms end-to-end behavior of the CGM Display App.


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

[Assistant] Content: The PharmaSafe CDSS development schedule is anchored to formal milestones with documented transition criteria. Progress is measured against these gates rather than calendar dates, ensuring the Clinical Decision Support System meets all quality and safety requirements before advancing to the next lifecycle phase.


[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 CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 5.2.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: The CogniTest Cognitive Assessment App shall operate within the memory, storage, and processing constraints of the iPadOS platform. Resource usage requirements are specified with numerical bounds and verified through profiling during system testing of the Cognitive Assessment Application.


[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 BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clause 5.1.4.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: The C (embedded, safety-critical) compiler, test framework, and coverage analysis tools used for the BrachyDose HDR Afterloader Controller are qualified per Clause 5.1.4. Qualification includes comparison of tool output against known-correct reference results and documentation of tool version, configuration, and any known limitations affecting the HDR Brachytherapy Afterloader Firmware verification.


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

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

"The VentAssist Pro detailed design per Clause 5.4 subdivides each software item into software units (Clause 5.4.1). Detailed design documents interfaces (Clause 5.4.3) and is verified per Clause 5.4.4 by reviewers independent of the author."

[Assistant]
Verdict: PASS
Note: Content includes detailed design per Clause 5.4 as required for Class C; correctly specifies independent review for Class C. Standards references are accurate.


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

[User]
Expand requirement SRS-PERF-001: "computational accuracy requirement" (Category: performance)
Project: BrachyDose HDR Afterloader Controller | HDR Brachytherapy Afterloader Firmware | Class C
Controlling radioactive source stepping positions and dwell times for high-dose-rate brachytherapy. Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

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

[Assistant]
Description: Output accuracy of the HDR Brachytherapy Afterloader Firmware shall meet or exceed the specified tolerance for all measurement parameters across operating conditions.
Rationale: Measurement accuracy directly affects clinical decisions based on the HDR Brachytherapy Afterloader Firmware output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
Source: Regulatory


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

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

"Detailed design for the CaloriePal documents algorithms, data structures, and internal interfaces for each software unit per Clause 5.4.2."

[Assistant]
Verdict: FAIL
Note: Content mandates detailed design per Clause 5.4.2 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

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

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

[Assistant]
Description: Communication with the guard position switches over safety PLC I/O shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Conveyor Safety Interlock Software output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Review this documentation excerpt for the OxyPure Controller (oxygen concentrator controller, Class C):

"Architecture for the OxyPure Controller transforms requirements into a software architecture per Clause 5.3.1. Interfaces between software items are defined per Clause 5.3.2. SOUP functional requirements are specified per Clause 5.3.3. The architecture is verified per Clause 5.3.6."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the OxyPure Controller (oxygen concentrator controller, Class C). Standards references are accurate.


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

[User]
Write a SDP section on development methodology for Class A for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clause 5.1.1.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: The OBDView Diagnostic Display follows an agile-inspired iterative lifecycle with lightweight phase gates suited to Class A software. Milestones are Requirements Baseline, Implementation Freeze, and System Test Complete. No architecture review or detailed design review gate is required, as these artifacts are not mandated for Class A.


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

[User]
Expand requirement SRS-DATA-003: "stored data corruption detection" (Category: data)
Project: CleanRoom Particle Counter Logger | Cleanroom Environmental Logger | Class A
Logging and displaying airborne particle counts for cleanroom compliance. Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

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

[Assistant]
Description: The CleanRoom Particle Counter Logger shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


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

[User]
Review this documentation excerpt for the DialysisGuard (hemodialysis machine controller, Class C):

"The lifecycle processes for the DialysisGuard comply with ISO 14971-2."

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

"Per IEC 62304 Clause 7.1, risk analysis is performed. Per IEC 62304 Clause 7.1, hazards are identified. Per IEC 62304 Clause 7.1, causes are documented. Per IEC 62304 Clause 7.1, the PillRemind risk analysis is complete."

[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 PillRemind.


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

[User]
Write a THREAT section on threat model data flow decomposition for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: The RetinaStim Visual Prosthesis Controller threat model decomposes the Retinal Prosthesis Controller Firmware into data flow diagrams showing all external entities, processes, data stores, and data flows. Each data flow crossing a trust boundary is analyzed for threats. The decomposition covers miniature camera input, internal processing, and output via RF coil to implant.


[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 C -- comprehensive controls for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: The RetinaStim Visual Prosthesis Controller Retinal Prosthesis Controller Firmware safety requirements per Clause 5.2.3 enumerate controls for every hazardous failure mode: data corruption detection, processing timeout monitoring, output range validation, and independent safety channel verification. Each control is verified through unit testing, integration testing, and system testing with independent review.


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

[User] Does IEC 62304 have sub-parts like IEC 62304-1 or IEC 62304-2?

[Assistant] No. IEC 62304 is a single-part standard. There is no IEC 62304-1, IEC 62304-2, or any sub-part. The correct citation is IEC 62304:2006+AMD1:2015. Amendment 1 (2015) added provisions for safety classification but did not create sub-parts.


[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 user interaction 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: The AnticoagCalc INR Dose Adjuster Anticoagulation Dosing Support Tool presents information to the user via FHIR Observation API and accepts user input through defined interaction patterns. User interaction requirements are traceable to the usability engineering file per IEC 62366-1:2015+AMD1:2020.


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

[User]
Expand requirement SRS-FUNC-005: "measurement data archival" (Category: functional)
Project: TriagePro Emergency Scoring App | Emergency Department Triage SaMD | Class B
Guiding emergency department triage scoring using the Manchester Triage System protocol. Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

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

[Assistant]
Description: All processed measurements shall be stored with timestamps in a persistent log accessible through HL7 FHIR to hospital EMR for clinical review and regulatory audit.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Emergency Department Triage SaMD.
Priority: Desirable
Acceptance Criterion: Logged data is retrievable after power cycle, with all timestamps accurate to within 1 second of the reference clock.
Source: User need


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

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

"Statement coverage of 90% and branch coverage of 80% are mandatory for the MedInventory."

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

[User]
Write a SRS section on resource constraints and scalability for FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: Computational resource requirements for the FactoryTemp Industrial Temperature Monitor define the maximum CPU utilization, RAM consumption, and flash/disk usage permitted on PLC (Allen-Bradley). The Industrial Temperature Monitoring Firmware must meet all functional and timing requirements within these resource envelopes.


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

[User]
Expand requirement SRS-FUNC-002: "power-on self-test sequence" (Category: functional)
Project: RoomBoard Digital Signage | Patient Room Digital Signage | Class A
Displaying non-clinical patient information on bedside screens. Hospital room digital signage displaying patient name, care team, and daily schedule. Display-only, no clinical data entry.

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 primary sensor communication, memory integrity, and MQTT connectivity before the Patient Room Digital Signage transitions to its operational state.
Rationale: A power-on self-test confirms hardware and software readiness before the Patient Room Digital Signage begins use.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[User]
Write a SAD section on SOUP component integration and requirements for WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

[Assistant] Content: The WeatherNode Microclimate Station Weather Station Firmware integrates SOUP components per Clause 5.3.3 with specified functional requirements and per Clause 5.3.4 with documented hardware/software prerequisites. Each SOUP item's known anomaly list has been evaluated per Clause 7.1.3 and documented in the risk management file.


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

[User]
Write a SDP section on requirements elicitation and documentation for InsuPrecise Insulin Pump Controller, a Class C Insulin Pump Controller Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

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


[System] You are an IEC 62304 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 BloodBank Manager (blood bank inventory system, Class A):

"The software is released. The release is documented. The release is verified. The release package is prepared. The release is approved. The BloodBank Manager software release follows the process."

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


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

[User]
Write a SDP section on safety classification process and documentation for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 4.3.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: The safety classification of the WeightAlert Neonatal Scale was determined per IEC 62304 Clause 4.3, considering the software's contribution to hazardous situations identified in the ISO 14971 risk analysis. The classification is documented in the risk management file and reviewed whenever the intended use, system architecture, or risk profile of the Neonatal Scale Firmware changes.


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

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

"Referenced standards for the NeuroStim Programmer include IEC 62304:2006+AMD1:2015 (software lifecycle), ISO 14971:2019 (risk management), and ISO 13485:2016 (QMS). IEC 81001-5-1:2021 is referenced for cybersecurity considerations."

[Assistant]
Verdict: PASS
Note: Content uses the correct IEC 62304 citation; correctly references ISO 14971:2019; correctly references ISO 13485:2016. 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):

"The software architecture is designed following best engineering practices. Modules are structured to support maintainability and extensibility as needed."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed" provide no project-specific information about the PacePilot pacemaker programmer. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

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

"The LabView Portal development follows ISO 14971-1 for the software lifecycle."

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

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

"Comprehensive unit tests shall be developed for every software module of the HydroLog."

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


[System] You are a 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: "measurement accuracy specification" (Category: performance)
Project: InfuRate IV Flow Calculator | Infusion Rate Calculator | Class B
Calculating IV infusion rates from prescribed doses, concentrations, and patient parameters. Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

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

[Assistant]
Description: Computational results produced by the InfuRate IV Flow Calculator shall be accurate to within the specified tolerance, validated against reference calculations.
Rationale: Inaccurate output from the Infusion Rate Calculator could lead to incorrect clinical actions, making accuracy a safety-critical requirement.
Priority: Mandatory
Acceptance Criterion: Statistical analysis of 500 measurements shows mean error within tolerance and standard deviation within specified limits.
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 requirements conventions and identification scheme for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: Requirements in this SRS are identified using the format SRS-AQU-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 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 CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clause 5.2.2.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

[Assistant] Content: Data exchanged by the CleanRoom Particle Counter Logger via RS-485 Modbus conforms to defined formats documented in this SRS. The Cleanroom Environmental Logger validates incoming data against the format specification and rejects malformed messages with a logged error. Output data formats are deterministic and reproducible.


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

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

"REQ-SRS-001: The RadBeam Planner shall display the current reading within 2 seconds of receiving data from the sensor interface. Acceptance criterion: measured latency from data receipt to display update is less than 2000 ms in 95% of test runs. Priority: Mandatory. Source: User need."

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

"The development plan references IEC 62304 Clause 5.1.12 and Clause 5.10 for the WoundTrack."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.1.12 and 5.10, neither of which exists. Clause 5.1 has 5.1.1 through 5.1.11 only. Clause 5 ends at 5.8. 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 risk control coverage verification for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

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


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

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

"The CaloriePal architecture is defined. The CaloriePal architecture is documented. The CaloriePal architecture is verified. The CaloriePal architecture is reviewed. The CaloriePal architecture is approved."

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


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

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for MindCalm Meditation Timer, a Class A Meditation Wellness App. Reference IEC 62304 Clause 5.1.1.
Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

[Assistant] Content: For the MindCalm Meditation Timer, this SDP defines a streamlined development process aligned with the Class A requirements of IEC 62304. The Meditation Wellness App is used for Guided meditation timing with optional passive biometric display, presenting no pathway to patient harm. Deliverables are limited to the SDP itself, a Software Requirements Specification, system test records, and the software release package. No architecture document, detailed design, or unit test reports are produced.