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

[User]
Write a SRS section on data retention and integrity requirements for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: The CardioCloud ECG Analysis Service Cloud ECG Analysis SaMD data requirements address storage, integrity, and lifecycle management. All persistent data is validated on read, and write operations use atomic commit mechanisms to prevent partial updates during Automated arrhythmia detection and ECG interpretation as a cloud service for remote clinics.


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

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

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

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


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

[User] What sub-clauses exist under IEC 62304 Clause 5.1?

[Assistant]
IEC 62304 Clause 5.1 (Software development planning) contains the following sub-clauses:

- Clause 5.1: Software development planning
- Clause 5.1.1: Software development plan
- Clause 5.1.2: Keep software development plan updated
- Clause 5.1.3: Software development plan reference to system design and development
- Clause 5.1.4: Software development standards, methods and tools planning
- Clause 5.1.5: Software integration and integration testing planning
- Clause 5.1.6: Software verification planning
- Clause 5.1.7: Software risk management planning
- Clause 5.1.8: Documentation planning
- Clause 5.1.9: Software configuration management planning
- Clause 5.1.10: Supporting items to be controlled
- Clause 5.1.11: Software configuration item control before verification

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


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

[User]
Expand requirement SRS-FUNC-001: "startup diagnostic verification" (Category: functional)
Project: DreamLog Sleep Monitor | Sleep Tracking Display App | Class A
Visualizing sleep quality data for personal wellness awareness. Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

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

[Assistant]
Description: The DreamLog Sleep Monitor startup sequence shall include diagnostic checks of all critical subsystems and report any detected faults before allowing operational use.
Rationale: A power-on self-test confirms hardware and software readiness before the Sleep Tracking Display App begins use.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

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

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


[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 ThermoGuard software components shall be integration-tested using continuous integration pipelines with automated interface verification."

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


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

[User]
Write a SDP section on purpose and scope for Class B with moderate documentation for GaitSense Walking Analysis, a Class B Gait Analysis Insole Firmware. Reference IEC 62304 Clause 5.1.1.
Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

[Assistant] Content: The GaitSense Walking Analysis Software Development Plan defines the processes, tools, and deliverables governing development of the Gait Analysis Insole Firmware in accordance with IEC 62304 Clause 5.1.1. Given the Class B safety classification -- where the software can contribute to a non-serious injury through Quantitative gait analysis using instrumented insoles for orthopedic and rehabilitation assessment -- this plan mandates architectural design documentation, integration testing, and software requirements traceability with sufficient rigor to mitigate identified risks.


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

[User]
Expand requirement SRS-INTF-002: "sensor data link requirements" (Category: interface)
Project: 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: Communication with the primary sensor over Bluetooth OBD-II adapter shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Vehicle Diagnostic Display App 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 requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-FUNC-003: "continuous data sampling from force-sensitive resistors (FSR array)" (Category: functional)
Project: GaitSense Walking Analysis | Gait Analysis Insole Firmware | Class B
Quantitative gait analysis using instrumented insoles for orthopedic and rehabilitation assessment. Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

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

[Assistant]
Description: Data from the force-sensitive resistors (FSR array) shall be acquired by the GaitSense Walking Analysis at the configured rate, with each sample timestamped and queued for processing.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Gait Analysis Insole Firmware.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

[User]
Expand requirement SRS-FUNC-004: "user-configurable operating parameters" (Category: functional)
Project: WasteTrack Biohazard Logger | Biohazard Waste Tracking App | Class A
Logging and tracking biohazard waste container chain of custody. Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental 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: Configuration changes to the WasteTrack Biohazard Logger shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the Biohazard Waste Tracking App to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

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

"In accordance with IEC 62304:2020, verification activities include system testing."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304:2020" which is incorrect. No 2020 edition exists. Current: IEC 62304:2006+AMD1: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 SAD section on SOUP component integration and requirements for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

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


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

[User]
Write a SDP section on internal SOPs and procedures for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clause 5.1.2.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: Company-internal standard operating procedures supplement the international standards for the LabStream LIS Middleware project. SOP-010 through SOP-013 address development planning, risk management, configuration management, and verification planning. All SOPs are part of the ISO 13485 quality management system and are binding on the Laboratory Information Middleware development team.


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

[User]
Write a SDP section on change control and trend analysis for problems for InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clauses 9.4, 9.6.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: All InfuRate IV Flow Calculator problem corrections enter the change control process per Clause 9.4 before integration into the baseline. Trend analysis per Clause 9.6 tracks defect density, time-to-resolution, and defect category distribution across the Infusion Rate Calculator development lifecycle to drive process improvement.


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

[User]
Review this documentation excerpt for the GlucoTrack CGM (continuous glucose monitor display, Class B):

"In accordance with ISO 13485-1, verification activities include system testing."

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


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

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

"Software requirements for the InfuSafe Controller are defined per Clause 5.2.1 and documented with the content required by Clause 5.2.2. Risk control measures are included in requirements per Clause 5.2.3. Requirements are verified per Clause 5.2.6."

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


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

[User]
Expand requirement SRS-INTF-001: "clinical system integration interface" (Category: interface)
Project: PulmoCheck Spirometry Analyzer | Spirometry Analysis Software | Class B
Analysis and interpretation of spirometry test data with predicted value comparison. Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

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


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

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

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

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


[System] You are 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 AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

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


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

[User]
Write a SDP section on minimal deliverables list for Class A for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clause 5.1.8.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The TrainCert Staff Certification Tracker documentation set is limited to the deliverables required for Class A: the SDP, SRS, system test records, software release record, and the risk management file. No architecture document, detailed design specification, unit test report, or integration test report is produced for this Training Certification 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 HydroLog (hydration tracking wellness app, Class A):

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

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


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

[User]
Write a SDP section on development methodology for Class C with full V-model for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clause 5.1.1.
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 follows a strict V-model lifecycle with no phase abbreviations permitted. Requirements trace to architecture, architecture traces to detailed design, and each trace is verified by independent reviewers. Unit testing with coverage targets, integration testing, and system testing form the ascending verification arm, each gated by formal review of the ICU Ventilator Controller Software test results.


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

"IEC 62311-1 Section 5.7 requires all software units to be verified."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62311-1" which is incorrect. IEC 62311 covers EMF exposure limits, not medical device software. All references must be corrected.


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

[User]
Write a SDP section on risk management integration into the lifecycle for PharmLog Medication History Viewer, a Class A Medication History Viewer. Reference IEC 62304 Clauses 7.1, 7.1.1.
Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

[Assistant] Content: Software risk management activities are integrated throughout the PharmLog Medication History Viewer 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 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on independent review process for Class C for AnesBot Automated Anesthesia Controller, a Class C Automated Anesthesia Delivery Software. Reference IEC 62304 Clause 5.1.1.
Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

[Assistant] Content: The AnesBot Automated Anesthesia Controller review process mandates independent technical review for all Class C deliverables. The independent reviewer has competence in C++ (real-time) development and IEC 62304 compliance but is not a member of the Automated Anesthesia Delivery Software development team. Review records include reviewer qualifications, findings, actions taken, and formal sign-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 purpose of the SRS document for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clause 5.2.1.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: This document specifies the software requirements for the AquaGuard Water Quality Monitor Water Quality Monitoring Firmware as required by IEC 62304 Clause 5.2.1. It serves as the primary input to design and the primary reference for verification test case derivation. All requirements are verifiable, traceable, and configuration-controlled.


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

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

"The LabView Portal requires integration testing at each build increment. Interface tests shall cover normal operation, boundary conditions, and fault scenarios."

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


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

[User]
Write a SDP section on minimal deliverables list for Class A for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clause 5.1.8.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: Documentation planning per Clause 5.1.8 for the BillingBridge Claims Processor 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

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

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

[Assistant]
Description: An independent hardware watchdog shall monitor the TransVent Transport Ventilator main processing loop, triggering a safe-state reset if the software fails to service the watchdog within the specified timeout.
Rationale: Hardware-independent monitoring ensures that a frozen main processor cannot leave the Transport Ventilator Firmware in an unsafe operating state.
Priority: Mandatory
Acceptance Criterion: Watchdog triggers safe-state reset within the specified timeout when the main loop is intentionally blocked, verified across 20 iterations.
Source: Risk control


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

[User]
Write a SDP section on verification strategy for Class C -- unit, integration, and system with coverage for ChemoFlow Infusion Controller, a Class C Chemotherapy Infusion Pump Firmware. Reference IEC 62304 Clauses 5.5, 5.5.2, 5.6, 5.7.
Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

[Assistant] Content: The ChemoFlow Infusion Controller Chemotherapy Infusion Pump Firmware undergoes three-tier verification per IEC 62304 Class C requirements. Unit verification per Clause 5.5 achieves statement coverage >= 90%, branch coverage >= 80%, and MC/DC coverage >= 80%. Integration testing per Clause 5.6 validates interfaces between software items. System testing per Clause 5.7 exercises all requirements. Each tier is independently reviewed.


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

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

"Per IEC 62304 Clause 5.1.1, the OxyPure Controller development plan defines the development process. Per IEC 62304 Clause 5.1.1, this plan establishes development activities. Per IEC 62304 Clause 5.1.1, the software development is governed by this plan. Per IEC 62304 Clause 5.1.1, all development follows this plan."

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


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

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

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


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

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

"REQ-SRS-056: Upon detecting a communication timeout with the sensor module, the SleepWell shall display a warning indicator within 1 second and log the event. Acceptance criterion: simulate timeout and verify warning display timing and log entry. 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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"The CardioPulse Monitor configuration management plan identifies all configuration items per Clause 8.1.1. SOUP items are tracked per Clause 8.1.2. Change control follows Clause 8.2 with traceability per Clause 8.2.4. Configuration status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the CardioPulse Monitor (cardiac rhythm monitor, Class B). Standards references are accurate.


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

[User]
Expand requirement SRS-SAFE-002: "fault response and safe shutdown" (Category: safety)
Project: RadOnco Cloud Treatment Planner | Cloud Radiation Treatment Planning SaMD | Class C
Cloud-based Monte Carlo dose calculation and treatment plan optimization for radiation oncology. Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

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 Cloud Radiation Treatment Planning SaMD shall enter a defined safe state within the maximum allowable transition time when a critical fault is detected, ensuring no hazardous output persists.
Rationale: Fail-safe behavior is essential to prevent the Cloud Radiation Treatment Planning SaMD from causing harm when its software detects an unrecoverable error.
Priority: Mandatory
Acceptance Criterion: Safe state transition completes within the specified time limit for each defined critical fault, verified by fault injection during operation.
Source: Risk control


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

[User]
Expand requirement SRS-INTF-001: "external system data exchange" (Category: interface)
Project: PharmLog Medication History Viewer | Medication History Viewer | Class A
Read-only display of medication dispensing history. Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

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 FHIR MedicationDispense API, supporting standard message formats.
Rationale: External system connectivity is required for the Medication History Viewer to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

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

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

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


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

[User]
Write a SDP section on internal SOPs and procedures for LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clause 5.1.2.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: Company-internal standard operating procedures supplement the international standards for the LinacControl Beam Delivery System project. SOP-010 through SOP-013 address development planning, risk management, configuration management, and verification planning. All SOPs are part of the ISO 13485 quality management system and are binding on the Linear Accelerator Control Software development team.


[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: "power-on self-test sequence" (Category: functional)
Project: AirSentry Urban Air Quality Station | Air Quality Monitoring Station Firmware | Class A
Continuous measurement and public reporting of urban air quality parameters. IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

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

[Assistant]
Description: Upon power-up, the AirSentry Urban Air Quality Station shall execute a self-test sequence verifying the integrity of the Alphasense NO2-B43F interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Air Quality Monitoring Station Firmware from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

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

"The NurseCall Hub software architecture per Clause 5.3 decomposes the system into software items with documented interfaces."

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

[Assistant] Content: Safety requirements are not applicable to the PathSlide Digital Pathology Viewer because the Class A Digital Pathology Viewer cannot contribute to a hazardous situation. The software does not implement risk control measures per Clause 5.2.3. All output is informational and used for Display of digitized pathology slides for reference viewing without clinical decision support.


[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: "access control and authorization" (Category: security)
Project: SunGuard UV Index Display | UV Exposure Display Firmware | Class A
Passive display of UV index for personal awareness. Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the SunGuard UV Index Display, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the UV Exposure Display Firmware operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed" provide no project-specific information about the PillRemind medication reminder app. Content must reference specific IEC 62304 clauses, concrete activities, and measurable 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 HeartLink (cardiac telemetry system, Class B):

"Software requirements for the HeartLink are defined per Clause 5.2.1 and documented with the content required by Clause 5.2.2. Risk control measures are included in requirements per Clause 5.2.3. Requirements are verified per Clause 5.2.6."

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


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

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

[Assistant] Content: Data exchanged by the BrachyDose HDR Afterloader Controller via stepper motor driver conforms to defined formats documented in this SRS. The HDR Brachytherapy Afterloader Firmware validates incoming data against the format specification and rejects malformed messages with a logged error. Output data formats are deterministic and reproducible.


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

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

"The RadView DICOM shall undergo static code analysis with all warnings treated as errors, followed by unit testing with decision coverage of at least 75%."

[Assistant]
Verdict: FAIL
Note: Content mandates static analysis and unit testing with decision coverage for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Unit verification (Clause 5.5) and static analysis requirements 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 SRS section on latency and throughput requirements for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clause 5.2.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

[Assistant] Content: The ClinTrial EDC Platform performance requirements define measurable bounds on processing latency, data throughput, and memory utilization. The Clinical Trial EDC Web Platform must sustain these performance levels under peak operating conditions on AWS ECS + RDS PostgreSQL + S3 throughout the full duration of Electronic capture and management of clinical trial data across multiple investigator sites.


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

[User]
Review this documentation excerpt for the PhysioTrack Rehab (rehabilitation tracking system, Class B):

"REQ-SRS-056: Upon detecting a communication timeout with the sensor module, the PhysioTrack Rehab shall display a warning indicator within 1 second and log the event. Acceptance criterion: simulate timeout and verify warning display timing and log entry. 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 SRS section on data processing and transformation requirements for AnesBot Automated Anesthesia Controller, a Class C Automated Anesthesia Delivery Software. Reference IEC 62304 Clause 5.2.2.
Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

[Assistant] Content: Processing requirements for the AnesBot Automated Anesthesia Controller Automated Anesthesia Delivery Software cover data acquisition, filtering, computation, and presentation. Each processing step has specified input ranges, output tolerances, and error conditions. Data integrity is maintained throughout the processing pipeline.


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

[User]
Expand requirement SRS-SAFE-002: "hardware watchdog safety mechanism" (Category: safety)
Project: BeamPlan Radiation Treatment Planner | Radiation Treatment Planning Software | Class C
Calculating optimal radiation beam configurations and dose distributions for cancer treatment. Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

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 Radiation Treatment Planning Software shall employ a hardware watchdog independent of the main processor to detect software hang conditions and enforce safe-state recovery.
Rationale: Hardware-independent monitoring ensures that a frozen main processor cannot leave the Radiation Treatment Planning Software in an unsafe operating state.
Priority: Mandatory
Acceptance Criterion: Watchdog triggers safe-state reset within the specified timeout when the main loop is intentionally blocked, verified across 20 iterations.
Source: Risk control


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

[User]
Expand requirement SRS-FUNC-005: "configuration persistence and validation" (Category: functional)
Project: AirSentry Urban Air Quality Station | Air Quality Monitoring Station Firmware | Class A
Continuous measurement and public reporting of urban air quality parameters. IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

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 AirSentry Urban Air Quality Station shall allow authorized users to configure operating parameters via 4G LTE and persist settings across power cycles.
Rationale: Configurable parameters allow the Air Quality Monitoring Station Firmware to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

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

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


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

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

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

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


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

[User]
Write a SDP section on development methodology for Class A for WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clause 5.1.1.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

[Assistant] Content: An iterative development approach with defined phase gates is adopted for the WeatherNode Microclimate Station, appropriate for the Class A classification where system-level verification is the primary quality gate. Each iteration produces a testable increment of the Weather Station Firmware functionality, with reviews at Requirements Complete, Implementation Complete, and Release Readiness milestones.


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

[Assistant] Content: The WaveReview EEG Archive Viewer system overview identifies all external entities interacting with the EEG Archive Viewer: input sources (external data), output destinations (desktop GUI), and the Windows/Linux desktop execution environment. Requirements for each external interface are documented in the interface requirements section.


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

[User]
Write a FMEA section on risk control measures and implementation for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: The InhaleSense Smart Inhaler Tracker risk controls per Clause 7.2.1 address each failure mode with unacceptable residual risk. Software-implemented controls per Clause 7.2.2 include defensive coding measures, plausibility checks, and safe-state transitions. Each control is documented as a software requirement and verified for the Smart Inhaler Adherence Tracker.


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

[User]
Expand requirement SRS-FUNC-003: "audit trail and data export" (Category: functional)
Project: HandGrip Strength Dynamometer | Hand Dynamometer Firmware | Class B
Measuring hand grip strength and fatigue patterns for rehabilitation progress tracking. Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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

[Assistant]
Description: The Hand Dynamometer Firmware shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via BLE 5.0.
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 RadView DICOM (DICOM image viewer, Class A):

"The lifecycle processes for the RadView DICOM comply with IEC 62304-5."

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

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

[Assistant] Content: The FetalGuard Heart Rate Monitor Class B safety requirements include controls for data integrity, range validation, and fail-safe behavior when external system communication is lost. Each requirement traces to a hazard identified in the risk analysis and is verified during integration or system testing of the Fetal Heart Rate Monitor Firmware.


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

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

"System testing for the StepTrack establishes tests per Clause 5.7.1. The software problem resolution process is used per Clause 5.7.2. Retesting after changes follows Clause 5.7.3. Test records conform to Clause 5.7.5."

[Assistant]
Verdict: PASS
Note: Content limits verification to system testing per Clause 5.7. Standards references are accurate.


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

[User]
Write a SDP section on risk control verification and traceability for InsuPrecise Insulin Pump Controller, a Class C Insulin Pump Controller Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

[Assistant] Content: Risk control verification for the InsuPrecise Insulin Pump Controller per Clause 7.3.1 is performed as part of the applicable testing levels. Each risk control measure is traced per Clause 7.3.2 from the ISO 14971 risk analysis through the SRS to the test result confirming its implementation in the Insulin Pump Controller Firmware.


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

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

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

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


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

"In accordance with IEC 62304-5, verification activities include system testing."

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


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

[User]
Expand requirement SRS-PERF-002: "data processing timing constraint" (Category: performance)
Project: DialyFlow Dialysis Fluid Controller | Hemodialysis Fluid Controller Firmware | Class C
Controlling dialysate composition, flow rates, and ultrafiltration in hemodialysis. Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

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

[Assistant]
Description: End-to-end latency from conductivity sensors (x2) data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Bounded processing latency ensures the Hemodialysis Fluid Controller Firmware provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


[System] You are 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 InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: Verification of risk control measures for the InfuRate IV Flow Calculator 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 Infusion Rate Calculator.


[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: "output refresh interval for PulseRing Smart Ring Monitor" (Category: functional)
Project: PulseRing Smart Ring Monitor | Wearable Smart Ring Firmware + Companion App | Class B
Continuous photoplethysmography-based heart rate and SpO2 monitoring via wearable ring with mobile companion. Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

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

[Assistant]
Description: The PulseRing Smart Ring Monitor display shall present current readings on BLE 5.3 within the specified maximum update latency.
Rationale: Display freshness is critical for the Wearable Smart Ring Firmware + Companion App to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


[System] You are a 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 OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Safety requirements are not applicable to the OBDView Diagnostic Display because the Class A Vehicle Diagnostic Display App cannot contribute to a hazardous situation. The software does not implement risk control measures per Clause 5.2.3. All output is informational and used for Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use without clinical decision support.


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

[User]
Write a SDP section on risk management integration into the lifecycle for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clauses 7.1, 7.1.1.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: Risk management for the AllergyCard Patient Allergy Viewer follows IEC 62304 Clause 7 and ISO 14971:2019. Hazard identification per Clause 7.1.1 is performed during requirements analysis and updated as the Patient Allergy Display design evolves. Risk control measures are traced to software requirements and verified through the testing activities defined in this plan.


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

[User]
Write a TRACE section on risk control coverage verification for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

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


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

[User]
Expand requirement SRS-FUNC-002: "measurement data archival" (Category: functional)
Project: GrowthChart Pediatric Viewer | Growth Chart Display App | Class A
Visual display of pediatric growth measurements on standard percentile charts. Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

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 FHIR Observation API for clinical review and regulatory audit.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Growth Chart Display App.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: SOUP anomaly evaluation for the LabStream LIS Middleware per Clause 7.1.3 reviews published defect lists for each third-party component. Anomalies that could affect the Laboratory Information Middleware safety or functionality are documented in the risk management file with corresponding risk control measures.


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

[User]
Expand requirement SRS-FUNC-001: "alarm generation and notification" (Category: functional)
Project: PainScale Digital Assessment Tool | Pain Assessment Tool | Class B
Standardized pain intensity and quality assessment with longitudinal tracking for treatment evaluation. Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

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 PainScale Digital Assessment Tool shall generate audible and visual alarms within the specified response time when a monitored parameter exceeds its configured threshold.
Rationale: Timely alarm generation is essential for the Pain Assessment Tool to alert clinicians to abnormal conditions requiring intervention.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


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

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

[Assistant] Content: The AIDose Chemotherapy Decision Support data flow begins at the input interface and terminates at the user-facing output. Intermediate processing stages -- including validation, filtering, and computation -- are implemented as separate software items with defined interfaces per Clause 5.3.2. The Cloud AI Chemotherapy Dosing SaMD data flow is documented to support traceability and integration testing.


[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 PacePilot (pacemaker programmer, Class C):

"The PacePilot integration test plan addresses Clause 5.6.1 through 5.6.7. Software units are integrated incrementally with testing at each step. Test content per Clause 5.6.4 covers data integrity, timing constraints, and fault tolerance. Test records meet Clause 5.6.7 requirements."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PacePilot (pacemaker programmer, Class C). 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: "clinical system integration interface" (Category: interface)
Project: VibeCheck Vibration Analyzer | Vibration Analysis Instrument Firmware | Class A
Vibration spectrum analysis of industrial machinery for predictive maintenance. Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer 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 VibeCheck Vibration Analyzer shall exchange data with external systems via BNC input using the specified message format with error handling.
Rationale: Interoperability enables integration of Vibration Analysis Instrument 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 a requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-PERF-001: "RAM and storage constraints" (Category: performance)
Project: PhysioTrack Rehabilitation Monitor | Physical Therapy Tracking System | Class B
Tracking exercise performance and range of motion during physical therapy for therapist review. Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

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

[Assistant]
Description: Peak memory consumption of the Physical Therapy Tracking System shall not exceed the allocated budget, with sufficient margin for stack overflow protection.
Rationale: Memory constraints are fixed by the nRF52840 + web dashboard hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

[User]
Expand requirement SRS-FUNC-006: "device configuration management" (Category: functional)
Project: SleepScore Apnea Screening Tool | Sleep Apnea Screening App | Class B
Screening for sleep apnea indicators using smartphone audio analysis, requiring sleep study confirmation. Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

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

[Assistant]
Description: Operating parameters of the Sleep Apnea Screening App shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Configurable parameters allow the Sleep Apnea Screening App to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User]
Write a SAD section on interface design between software items for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.3.2.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: Interfaces between PaceSet Pacemaker Programmer software items are specified per Clause 5.3.2 with defined data types, calling conventions, error return values, and thread safety requirements. The Cardiac Pacemaker Programmer Software internal interfaces include the RF telemetry wand abstraction layer, the processing API, and the presentation layer interface.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clause 7.1.1.
Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

[Assistant] Content: The FridgeGuard Temperature Logger FMEA scope is limited to confirmation that no software failure mode contributes to a hazardous situation, consistent with the Class A classification per Clause 7.1.1. The analysis covers data acquisition, processing, and display functions of the Cold Chain Temperature Logger and confirms that all failure effects are limited to loss of informational functionality.


[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: 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: The Ambulatory Blood Pressure Monitor Firmware sensor interface shall establish and maintain reliable communication with the pressure transducer via BLE 5.0.
Rationale: Reliable sensor communication is the foundation of the Ambulatory Blood Pressure Monitor 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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the BloodBank Manager (blood bank inventory system, Class A). 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-SEC-001: "user identity verification" (Category: security)
Project: AuditTrail QMS Event Logger | QMS Audit Trail Service | Class A
Capturing and archiving QMS events for regulatory audit trails. Microservice capturing and storing quality management system audit events. Logging and reporting 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: User authentication shall be enforced for all configuration changes to the AuditTrail QMS Event Logger, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the QMS Audit Trail Service operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

[User]
Write a SAD section on SOUP component integration and requirements for LabView Results Portal, a Class A Laboratory Results Viewer. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

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


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

[User]
Expand requirement SRS-FUNC-004: "alarm generation and notification" (Category: functional)
Project: FetalGuard Heart Rate Monitor | Fetal Heart Rate Monitor Firmware | Class B
Continuous external fetal heart rate monitoring during labor with clinical display. External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

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

[Assistant]
Description: The Fetal Heart Rate Monitor Firmware shall monitor all active parameters against user-configured thresholds and activate appropriate alarm signals when limits are breached.
Rationale: Alarm functionality is a safety-critical feature of the Fetal Heart Rate Monitor Firmware that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: Alarm triggers within the specified response time of a threshold crossing, measured over 50 test crossings with no false negatives.
Source: Risk control


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

"Unit testing for the HydroLog shall use mutation testing to ensure test suite effectiveness, targeting a mutation score of at least 85%."

[Assistant]
Verdict: FAIL
Note: Content mandates mutation testing at unit level 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 CardioPulse Monitor (cardiac rhythm monitor, Class B):

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

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


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

[User]
Write a SDP section on Class A classification justification and implications for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clause 4.3.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: The LabStream LIS Middleware software is classified as IEC 62304 Safety Class A because it cannot contribute to a hazardous situation. As a Laboratory Information Middleware used for Routing and auto-validating laboratory results between analyzers and the laboratory information system, the software provides informational output only and does not control any therapeutic function, deliver any treatment, or make any clinical decision that could cause harm if incorrect.


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

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

"The BloodBank Manager 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 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 system boundaries and external dependencies for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.2.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: The AirSentry Urban Air Quality Station software boundary encompasses the Air Quality Monitoring Station Firmware application executing on ESP32 + Raspberry Pi. External dependencies include Alphasense NO2-B43F hardware and solar charge controller. These external systems are treated as black boxes at the software boundary, with interface requirements specified in this SRS.


[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 FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clause 5.2.2.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: Requirements for external system integration with the FleetTrack GPS Tracking Module specify the API contracts, data formats, and error handling behavior for all outbound communication from the Fleet GPS Tracking Firmware. The software must handle connection timeouts, malformed responses, and authentication failures without affecting safety-relevant functions.


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

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

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

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

[User]
Write a SDP section on cybersecurity and health IT standards for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clause 5.1.2.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

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