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

[User]
Write a SDP section on minimal deliverables list for Class A for SupplyChain Procurement Portal, a Class A Supply Chain Procurement System. Reference IEC 62304 Clause 5.1.8.
Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

[Assistant] Content: Documentation planning per Clause 5.1.8 for the SupplyChain Procurement Portal yields a minimal Class A deliverable set: SDP, SRS, system test plan, system test report, software release record, and risk management file. Deliverables associated with architectural design, detailed design, unit testing, and integration testing are excluded.


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

[User]
Expand requirement SRS-INTF-001: "primary sensor interface protocol" (Category: interface)
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: Communication with the 4x load cells over USB shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Balance Training Platform Firmware data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Write a SDP section on hazard identification for the specific device for ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

[Assistant] Content: Software-related hazard causes for the ScheduleSync Appointment Manager Appointment Scheduling System are documented per Clause 7.1.2 and Clause 7.1.4. Risk control measures per Clause 7.2.1 address each identified cause through input validation, range checking, communication integrity verification, and fail-safe defaults.


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

[User]
Write a SDP section on problem reporting and investigation for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: Problems identified in the TransVent Transport Ventilator are reported per Clause 9.1 with anomaly description, affected component, severity, and reproduction steps. Investigation per Clause 9.2 determines root cause and impact. Relevant parties are advised per Clause 9.3 when the problem affects the Transport Ventilator Firmware safety or regulatory compliance.


[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 SleepWell (sleep quality display app, Class A):

"Configuration management is established. Configuration items are identified. Configuration items are controlled. Configuration status is reported. Configuration management is performed. Configuration is managed."

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


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

[User]
Write a SDP section on primary international standards applicable to development for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clause 5.1.2.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

[Assistant] Content: The software lifecycle for the DoseVerify In-Vivo Dosimetry System is executed under IEC 62304:2006+AMD1:2015, with risk management per ISO 14971:2019 integrated at each phase gate. Quality system requirements follow ISO 13485:2016, and usability validation of the In-Vivo Dosimetry Verification Software follows IEC 62366-1:2015+AMD1:2020.


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

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

"Risk control measures are implemented per IEC 62304-5 Clause 7."

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


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

[User]
Expand requirement SRS-SEC-002: "patient data protection" (Category: security)
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: Patient-identifiable data stored by the RetinaStim Visual Prosthesis Controller 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 Prosthesis Controller Firmware storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

[User]
Expand requirement SRS-FUNC-006: "configuration persistence and validation" (Category: functional)
Project: OBDView Diagnostic Display | Vehicle Diagnostic Display App | Class A
Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use. Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

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

[Assistant]
Description: The OBDView Diagnostic Display shall allow authorized users to configure operating parameters via Bluetooth OBD-II adapter and persist settings across power cycles.
Rationale: Configurable parameters allow the Vehicle Diagnostic Display App 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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

[User]
Review this documentation excerpt for the ArthroNav (surgical navigation system, Class C):

"Independent review is required for all Class C deliverables of the ArthroNav. System verification is performed by personnel not directly responsible for the development of the item under review. Code reviews are conducted by qualified engineers who were not the original authors."

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


[System] You are 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 GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clause 5.2.2.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: Security requirements for the GlucoSpot Continuous Glucose Display at the Class B/C level include cryptographic integrity verification of firmware, mutual TLS for external communications via push notifications, input sanitization on all external data paths, and a documented security incident response process.


[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: "display update rate for Nutritional Tracking Display App" (Category: functional)
Project: NutriView Food Diary | Nutritional Tracking Display App | Class A
Personal food logging and nutritional data visualization. Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

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

[Assistant]
Description: The NutriView Food Diary shall update the displayed values on the REST API at intervals no greater than the specified refresh period.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


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

[User]
Write a SDP section on configuration identification approach for PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clauses 8.1, 8.1.1.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

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


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

[User]
Write a SRS section on safety requirements for Class A -- confirms no safety functions for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: As a Class A system, the AutoclaveLog Cycle Recorder does not implement software safety functions. The Sterilization Cycle Data Logger presents acquired data for informational purposes only. No risk control measure per Clause 5.2.3 is implemented in software -- all identified risks are addressed by the informational-only design.


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

[User]
Write a SRS section on external system communication requirements for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clause 5.2.2.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

[Assistant] Content: The CochleaMap CI Fitting Software Cochlear Implant Fitting Software external communication requirements cover data exchange with remote systems. Each requirement specifies the message format, transport protocol, retry policy, and failure mode behavior, ensuring the Cochlear Implant Fitting Software degrades safely if communication is disrupted.


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

[User]
Write a SRS section on functional requirements overview for VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clause 5.2.2.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

[Assistant] Content: Functional requirements for the VibeCheck Vibration Analyzer are derived from the system requirements for Vibration spectrum analysis of industrial machinery for predictive maintenance and from risk control measures identified in the ISO 14971 analysis. Each requirement specifies a single function of the Vibration Analysis Instrument Firmware with measurable acceptance criteria.


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

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

"The regulatory framework for the DermaScan AI references IEC 62304:2006+AMD1:2015 Clauses 4 through 9 as applicable to Class B software. ISO 14971:2019 governs the risk management process. The quality system operates under ISO 13485:2016."

[Assistant]
Verdict: PASS
Note: Content correctly specifies Class B requirements; uses the correct IEC 62304 citation; correctly references ISO 14971:2019. 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 VentAssist Pro (ICU ventilator controller, Class C):

"Risk control verification for the VentAssist Pro follows Clause 7.3. Each risk control measure implemented in software (Clause 7.2.2) has a corresponding verification activity. Traceability from hazard through control measure to verification is documented per Clause 7.3.2."

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


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

[User]
Expand requirement SRS-INTF-002: "primary sensor interface protocol" (Category: interface)
Project: AssetTrack Equipment Inventory | Equipment Inventory System | Class A
Tracking location and status of medical equipment for inventory management. Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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

[Assistant]
Description: Communication with the camera barcode scanner over REST API shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Equipment Inventory System data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Write a SRS section on enhanced security for Class B and C 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: The Class B/C ChemoFlow Infusion Controller requires enhanced security controls beyond baseline requirements. The Chemotherapy Infusion Pump Firmware implements mutual authentication for all external interfaces, firmware integrity verification at startup, and secure update mechanisms. Vulnerability management follows IEC 81001-5-1:2021 throughout the product lifecycle.


[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 external interface architecture for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clause 5.3.2.
Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

[Assistant] Content: The SurgiPlan 3D Surgical Planner uses adapter patterns for all external interfaces: DICOM import, 3D visualization, PDF surgical plan export. Each adapter implements a common internal interface per Clause 5.3.2, isolating the 3D Surgical Planning SaMD processing logic from external protocol details.


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

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

"The DermaScan AI conforms to IEC 62304:2006+AMD1:2015. Safety classification per Clause 4.3 designates this skin lesion classifier as Class B. Risk management follows ISO 14971:2019 with guidance from ISO/TR 24971:2020."

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


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

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

"The HeartLink is designed to meet all applicable performance criteria. System requirements are addressed through appropriate design activities."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "generic phrasing" provide no project-specific information about the HeartLink cardiac telemetry system. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for AuditTrail QMS Event Logger, a Class A QMS Audit Trail Service. Reference IEC 62304 Clause 7.1.1.
Microservice capturing and storing quality management system audit events. Logging and reporting only.

[Assistant] Content: This software FMEA for the AuditTrail QMS Event Logger is a simplified analysis appropriate for Class A software that cannot contribute to a hazardous situation. The analysis confirms that identified software failure modes -- including input data processing errors and REST API rendering failures -- do not create patient safety risks, given the purely informational nature of the QMS Audit Trail Service output.


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

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

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


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

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

"The DialysisGuard addresses IEC 62304 Clause 6.4 for deployment validation and Clause 5.5.2.1 for automated regression testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 6.4 and 5.5.2.1, neither of which exists. Clause 6 has 6.1, 6.2, 6.3 only. IEC 62304 has no four-level numbering. 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 SAD section on SOUP risk evaluation and anomaly management for PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

[Assistant] Content: Risk evaluation of SOUP in the PainScale Digital Assessment Tool follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Pain Assessment Tool. Anomalies relevant to Standardized pain intensity and quality assessment with longitudinal tracking for treatment evaluation are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


[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 acceptance criteria and independent review for Class C for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clauses 5.5.3, 5.5.5, 5.7.4.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: The BreathSync ICU Ventilator Controller verification acceptance workflow proceeds bottom-up: unit tests are reviewed first (Clause 5.5.5), followed by integration tests (Clause 5.6.5), and finally system tests (Clause 5.7.4). At each level, an independent reviewer confirms pass/fail results, coverage metrics, and anomaly dispositions. No release of the ICU Ventilator Controller Software occurs until all levels are signed off.


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

[User]
Write a SRS section on system boundaries and external dependencies for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clause 5.2.2.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: The AllergyCard Patient Allergy Viewer system overview identifies all external entities interacting with the Patient Allergy Display: input sources (external data), output destinations (HL7 FHIR AllergyIntolerance API), and the Web kiosk (Chrome kiosk mode) execution environment. Requirements for each external interface are documented in the interface requirements section.


[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 SleepWell (sleep quality display 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 SleepWell 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 SleepWell.


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

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

"The ChemoCalc addresses IEC 62304 Clause 7.5 (operational qualification) through formal review."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 7.5 which does not exist. Clause 7 ends at 7.4. The reference must be corrected to a valid clause number.


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

"Software safety classification is performed per ISO 14901 Clause 4.3."

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


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

[User]
Write a SDP section on development platform and build infrastructure for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clause 5.1.4.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: Source code for the RadView DICOM Viewer Medical Image Viewer is written in C++/Qt and compiled for Windows/macOS/Linux desktop. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


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

[User]
Write a SRS section on system boundaries and external dependencies 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 software boundary encompasses the Cognitive Assessment Application application executing on iPadOS. External dependencies include touchscreen hardware and PDF export. These external systems are treated as black boxes at the software boundary, with interface requirements specified in this SRS.


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

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

"The LabView Portal test strategy is limited to system-level verification per Clause 5.7. Regression testing is performed when changes occur per Clause 5.7.3. Test record contents follow Clause 5.7.5. This is sufficient for Class A."

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


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

[User]
Expand requirement SRS-INTF-001: "clinical system integration interface" (Category: interface)
Project: PathCloud AI Histology Analyzer | Cloud SaMD Histopathology Analysis Platform | Class B
AI-assisted identification of suspicious regions in digitized histology slides for pathologist review. Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

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 PathCloud AI Histology Analyzer shall exchange data with external systems via REST API using the specified message format with error handling.
Rationale: Interoperability enables integration of Cloud SaMD Histopathology Analysis Platform data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User]
Write a SDP section on system test execution and acceptance for Class A for PharmLog Medication History Viewer, a Class A Medication History Viewer. Reference IEC 62304 Clauses 5.7, 5.7.4.
Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

[Assistant] Content: System tests for the PharmLog Medication History Viewer are executed on the iOS target with the Medication History Viewer operating in its intended configuration. Test results are recorded per Clause 5.7.5, and the system test is verified complete per Clause 5.7.4 when all requirements have a linked passing test. No unit tests or integration tests are produced, as Class A does not require these verification levels.


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

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

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

[Assistant]
Description: Patient-identifiable data stored by the PainRelief PCA Pump Controller shall be encrypted at rest using a validated cryptographic algorithm with a key length of at least 256 bits.
Rationale: Data-at-rest encryption is required to meet privacy regulations and protect patient confidentiality.
Priority: Mandatory
Acceptance Criterion: Cryptographic implementation validated against NIST standards with no known vulnerabilities in the selected algorithm.
Source: Regulatory


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

[User]
Write a SRS section on purpose of the SRS document for AutoPancreas Closed-Loop Glucose Controller, a Class C Artificial Pancreas Controller Firmware. Reference IEC 62304 Clause 5.2.1.
Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

[Assistant] Content: The purpose of this SRS is to establish the complete set of software requirements for the AutoPancreas Closed-Loop Glucose Controller, providing the basis for design, implementation, and verification of the Artificial Pancreas Controller Firmware. Requirements are organized by type and traced to their originating system requirement, risk control measure, or stakeholder need per Clause 5.2.1.


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

"Verification activities are conducted as needed to ensure quality and compliance. Testing approaches are selected based on best practices for the wound measurement imaging system."

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


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

[User]
Review this documentation excerpt for the ArthroNav (surgical navigation system, Class C):

"IEC 62304:2022 Section 5.2 requires all software units to be verified."

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


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

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

"REQ-SRS-034: The NeuroStim Programmer shall complete self-test diagnostics within 5 seconds of power-on and report any detected hardware faults. Acceptance criterion: inject simulated hardware faults and verify detection within the time limit. Priority: Mandatory. Source: System requirement."

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


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

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

"Architectural design for the NurseCall Hub defines interfaces between software items per Clause 5.3.2."

[Assistant]
Verdict: FAIL
Note: Content mandates architectural design documentation for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Architectural design (Clause 5.3) is not required for Class A.


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

[User]
Expand requirement SRS-FUNC-004: "configuration persistence and validation" (Category: functional)
Project: VitalBoard Patient Summary | Patient Summary Dashboard | Class A
Read-only display of patient vital sign history for clinical reference. Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

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 Patient Summary Dashboard shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Parameter flexibility is essential for the Patient Summary Dashboard to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User]
Expand requirement SRS-DATA-001: "record keeping duration" (Category: data)
Project: FallRisk Inpatient Assessment Tool | Fall Risk Assessment App | Class B
Calculating fall risk scores for hospitalized patients to guide nursing interventions. Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

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


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

[User]
Write a FMEA section on documenting failure modes and their effects for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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


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

[User]
Write a SDP section on hazard identification for the specific device for StepSync Activity Tracker, a Class A Wellness Activity Display App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

[Assistant] Content: The StepSync Activity Tracker risk analysis per Clause 7.1.2 identifies software causes of hazardous situations specific to the Wellness Activity Display App: data path corruption, timing violations, resource exhaustion, and incorrect state transitions. Each cause is linked to a risk control measure per Clause 7.2.1 and implemented as a verifiable software requirement.


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

[User]
Expand requirement SRS-INTF-003: "data export and interoperability" (Category: interface)
Project: SupplyChain Procurement Portal | Supply Chain Procurement System | Class A
Managing procurement of medical supplies with approval tracking. Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

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

[Assistant]
Description: The Supply Chain Procurement System shall support bidirectional data exchange with external systems over REST API.
Rationale: Interoperability enables integration of Supply Chain Procurement System data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User]
Write a FMEA section on risk control verification for ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

[Assistant] Content: Verification of risk control measures for the ScheduleSync Appointment Manager follows Clause 7.3.1. Each software-implemented control is tested to demonstrate that the hazardous condition is mitigated to an acceptable level. Verification results per Clause 7.3.3 are documented in the risk management file for the Appointment Scheduling System.


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

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

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

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


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

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

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

[Assistant]
Description: Data retention in the ClinTrial EDC Platform shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User] Can I cite ISO 14901 in my documentation?

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


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

[User]
Write a SDP section on primary international standards applicable to development for TriageAI Emergency Triage Assistant, a Class B ED Triage Decision Support App. Reference IEC 62304 Clause 5.1.2.
Tablet app assisting nurses in emergency department triage scoring based on vital signs and presenting symptoms.

[Assistant] Content: Applicable standards for the TriageAI Emergency Triage Assistant include IEC 62304:2006+AMD1:2015 (software lifecycle), ISO 14971:2019 (risk management), ISO 13485:2016 (quality management), and IEC 62366-1:2015+AMD1:2020 (usability engineering). These standards collectively define the processes, documentation, and verification expectations for the ED Triage Decision Support 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 SRS section on requirements conventions and identification scheme for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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


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

[User]
Write a SRS section on baseline security requirements 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 security requirements cover confidentiality, integrity, and availability of the Retinal Prosthesis Controller Firmware and its data per IEC 81001-5-1:2021. Requirements specify access control mechanisms, encryption for data at rest and in transit, session management, and audit logging.


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

[User]
Write a SDP section on risk management integration into the lifecycle for NeoVent Neonatal Ventilator, a Class C Neonatal Ventilator Firmware. Reference IEC 62304 Clauses 7.1, 7.1.1.
Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

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


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

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

"Verification activities follow IEC 62304 Clause 10.1 for continuous monitoring."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 10.1 which does not exist. IEC 62304 has no Clause 10. Standard ends at Clause 9. The reference must be corrected to a valid clause number.


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

[User]
Review this documentation excerpt for the ArthroNav (surgical navigation system, Class C):

"Maintenance activities follow ISO 13485-2 Clause 6."

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


[System] You are a 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: "record keeping duration" (Category: data)
Project: BSACalc Body Surface Area Tool | BSA Calculator Web App | Class B
Calculating body surface area for oncology dose determination. Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

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 BSACalc Body Surface Area Tool shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Write a TRACE section on gap identification and coverage analysis for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.7.4.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: Coverage analysis for the BeamPlan Radiation Treatment Planner per Clause 5.7.4 confirms that every SRS requirement maps to at least one test case with a passing result. Requirements implementing risk controls are additionally confirmed to have adequate test coverage. The Radiation Treatment Planning Software release is contingent on 100% requirement coverage with no open gaps.


[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: "data acquisition from primary sensor" (Category: functional)
Project: FallRisk Inpatient Assessment Tool | Fall Risk Assessment App | Class B
Calculating fall risk scores for hospitalized patients to guide nursing interventions. Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

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 FallRisk Inpatient Assessment Tool shall continuously sample primary sensor data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Calculating fall risk scores for hospitalized patients to guide nursing interventions.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

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

[Assistant] Content: The DialyFlow Dialysis Fluid Controller operates as a Hemodialysis Fluid Controller Firmware where Controlling dialysate composition, flow rates, and ultrafiltration in hemodialysis. The software interfaces with conductivity sensors (x2), flow meters (x2) and communicates via CAN bus, safety relay outputs. The operational environment, user population, and regulatory context described here constrain the requirements that follow.


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

[User]
Write a SRS section on baseline security requirements for RemotICU Continuous Monitoring Hub, a Class B Edge-to-Cloud ICU Monitoring Gateway. Reference IEC 62304 Clause 5.2.2.
Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

[Assistant] Content: The RemotICU Continuous Monitoring Hub Edge-to-Cloud ICU Monitoring Gateway implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

"Software problem resolution follows IEC 62304:2015 Clause 9."

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


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

[User]
Write a SDP section on risk management integration into the lifecycle for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clauses 7.1, 7.1.1.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

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


[System] You are 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 DialysisGuard (hemodialysis machine controller, Class C):

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

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


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

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

"Problem resolution follows established procedures and best practices. Issues are tracked and resolved in a timely manner as appropriate."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "best practices", "established procedures" provide no project-specific information about the CardioPulse Monitor cardiac rhythm monitor. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Expand requirement SRS-FUNC-001: "startup diagnostic verification" (Category: functional)
Project: WoundTrack Healing Analyzer | Wound Assessment App | Class B
Photographic wound measurement and healing progress tracking for clinical review. Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

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

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


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

[User]
Expand requirement SRS-INTF-002: "data export and interoperability" (Category: interface)
Project: TempWatch Body Temperature Logger | Temperature Logging Firmware | Class A
Passive logging and display of skin temperature trends for personal interest. Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

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

[Assistant]
Description: Data interoperability with clinical information systems shall be provided through I2C, supporting standard message formats.
Rationale: External system connectivity is required for the Temperature Logging 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 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: PressoTrack Blood Pressure Trending | Ambulatory Blood Pressure Monitor Firmware | Class B
Automated periodic blood pressure measurement and trending over 24 hours. Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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

[Assistant]
Description: Data interoperability with clinical information systems shall be provided through BLE 5.0, supporting standard message formats.
Rationale: Interoperability enables integration of Ambulatory Blood Pressure Monitor Firmware data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


[System] You are 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 WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clause 5.2.2.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

[Assistant] Content: The WeatherNode Microclimate Station functional requirements define what the Weather Station Firmware does in response to user inputs, sensor data, and system events. Requirements are organized by functional area: data acquisition, signal processing, display and output, and system management. Each requirement is individually testable.


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

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

[User]
Write a SAD section on interface design between software items for WoundTrack Healing Analyzer, a Class B Wound Assessment App. Reference IEC 62304 Clause 5.3.2.
Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

[Assistant] Content: The WoundTrack Healing Analyzer Wound Assessment App software item interfaces per Clause 5.3.2 are defined using typed data structures with explicit ownership semantics. Each interface specifies the pre-conditions, post-conditions, and error conditions. Interface compatibility is verified through integration testing per Clause 5.6.


[System] You are 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: "data logging and retrieval" (Category: functional)
Project: BSACalc Body Surface Area Tool | BSA Calculator Web App | Class B
Calculating body surface area for oncology dose determination. Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

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 BSA Calculator Web App shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via web form.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

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

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

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


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

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

"Applicable standards for the DermaScan AI are: IEC 62304:2006+AMD1:2015 for the software development lifecycle, ISO 14971:2019 for risk management, and ISO 13485:2016 for the quality management system. No sub-part standards are referenced as IEC 62304 and ISO 14971 are each single-part standards."

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the VentAssist Pro (ICU ventilator controller, Class C). 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 DialysisGuard (hemodialysis machine controller, Class C):

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

[User]
Write a SRS section on latency and throughput requirements for ECGInsight Rhythm Interpreter, a Class B ECG Interpretation Service. Reference IEC 62304 Clause 5.2.2.
Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

[Assistant] Content: The ECGInsight Rhythm Interpreter performance requirements define measurable bounds on processing latency, data throughput, and memory utilization. The ECG Interpretation Service must sustain these performance levels under peak operating conditions on Cloud (GCP with GPU) throughout the full duration of Automated preliminary interpretation of 12-lead ECG recordings for physician review and overread.


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

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

"Verification activities follow IEC 62304 Clause 5.5.2.1 for operational qualification."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.5.2.1 which does not exist. IEC 62304 has no four-level numbering. 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 SRS section on data retention and integrity requirements 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: Data requirements for the CogniTest Cognitive Assessment App specify retention periods, storage formats, and integrity controls for all persistent data managed by the Cognitive Assessment Application. Data integrity is ensured through checksums or cryptographic hashes, and corrupted data is detected before use in any processing function.


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

[User]
Write a SDP section on requirements verification approach for PowerTrack UPS Monitor, a Class A UPS Monitoring Software. Reference IEC 62304 Clause 5.2.6.
Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

[Assistant] Content: Requirements verification for the PowerTrack UPS Monitor is conducted per Clause 5.2.6 before the requirements baseline is established. The review confirms completeness, consistency, and testability. Any requirement failing these criteria is returned for rework before the UPS Monitoring Software proceeds to design.


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

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

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

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


[System] You are 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 VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.2.2.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: The VitalBoard Patient Summary shall operate within the memory, storage, and processing constraints of the Web SPA platform. Resource usage requirements are specified with numerical bounds and verified through profiling during system testing of the Patient Summary Dashboard.


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

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

"Risk management is performed in accordance with applicable standards and regulatory expectations. Hazard analysis is conducted as required by the regulatory framework."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "applicable standards", "as required by" 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-005: "audit trail and data export" (Category: functional)
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: All processed measurements shall be stored with timestamps in a persistent log accessible through RS-485 Modbus for clinical review and regulatory audit.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: 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 documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

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

[Assistant] Content: Performance requirements for the StrokeAlert CT Perfusion Analyzer specify maximum latencies, throughput rates, and resource consumption limits for the AI Stroke Triage CT Perfusion SaMD operating on AWS dedicated GPU + CloudFront + iOS/Android native app. Latency requirements define the maximum time from input event to output response for each critical processing path during Rapid automated CT perfusion analysis generating ischemic core and penumbra maps for acute stroke treatment decisions.


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

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

"Architectural design follows ISO 14971-1 Clause 5.3 for Class B 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 SDP section on requirements elicitation and documentation for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clauses 5.2.1, 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: Software requirements for the SurgiPlan 3D Surgical Planner are derived from system requirements, the risk management file, and stakeholder inputs per Clause 5.2.1. Each requirement specifies functional behavior, performance criteria, or interface constraints relevant to the 3D Surgical Planning SaMD and its use in Preoperative 3D planning of joint replacement procedures with implant sizing and alignment.


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

"The OxyPure Controller risk analysis per ISO 14971:2019 identifies software items that could contribute to hazardous situations per IEC 62304 Clause 7.1.1. Each identified cause is documented per Clause 7.1.4. Risk control measures are defined per Clause 7.2.1 and traced to software requirements."

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


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

[User]
Write a SAD section on external interface architecture for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clause 5.3.2.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: External interface architecture for the NeuroTune DBS Programmer Deep Brain Stimulator Programmer App wraps each physical interface in an abstraction layer. This design per Clause 5.3.2 decouples the application logic from hardware specifics of Dedicated Android tablet, enabling integration testing with simulated interfaces.


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

[User]
Review this documentation excerpt for the InfuSafe Controller (insulin infusion pump controller, Class C):

"Risk control measures are implemented per IEC 62304:2015 Clause 7."

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


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

[User]
Write a SAD section on interface design between software items for AnesBot Automated Anesthesia Controller, a Class C Automated Anesthesia Delivery Software. Reference IEC 62304 Clause 5.3.2.
Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

[Assistant] Content: Internal interface design for the AnesBot Automated Anesthesia Controller follows Clause 5.3.2. Each interface is documented with its function signature, parameter constraints, return value semantics, and thread safety guarantees. The Automated Anesthesia Delivery Software interfaces are designed for testability, supporting both integration testing and fault injection.


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

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

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


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

[User]
Write a SDP section on change control process for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

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


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clauses 5.7, 5.7.1.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

[Assistant] Content: System testing per Clause 5.7 is the sole verification activity for the HumidityMap Room Condition Logger. Tests validate that the Environmental Condition Logger meets all specified functional and performance requirements when deployed on ESP32 + cloud. Detailed design review (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6) are explicitly not required for this Class A system.


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

[User]
Write a SDP section on scope boundaries of the software system for AutoPancreas Closed-Loop Glucose Controller, a Class C Artificial Pancreas Controller Firmware. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

[Assistant] Content: Scope is limited to the AutoPancreas Closed-Loop Glucose Controller software items developed under this plan and released as a single configuration baseline. Peripherals, test jigs, and cloud infrastructure used during Automated closed-loop insulin delivery based on continuous glucose monitoring with predictive algorithms are addressed by separate system-level documentation and are not governed by IEC 62304 Clause 5.1.1 activities described herein.