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

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

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

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


[System] You are a regulatory 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 WaterPure Quality Logger, a Class A Water Quality Data Logger. Reference IEC 62304 Clause 5.2.2.
Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

[Assistant] Content: The WaterPure Quality Logger Water Quality Data Logger external communication requirements cover data exchange with remote systems. Each requirement specifies the message format, transport protocol, retry policy, and failure mode behavior, ensuring the Water Quality Data Logger degrades safely if communication is disrupted.


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

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

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

[Assistant]
Description: Communication with the primary sensor over REST API shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Consent Document Viewer data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
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 documenting failure modes and their effects for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: Documentation of TrainCert Staff Certification Tracker failure modes follows Clause 7.1.4. Each entry in the FMEA register includes: the software item, the failure mode, the potential cause(s), the effect on the Training Certification System during Tracking and reporting on staff training certifications and renewals, severity and probability ratings, and references to applicable risk control measures.


[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 CalibrationTracker Equipment Logger, a Class A Calibration Record System. Reference IEC 62304 Clause 5.1.2.
Web application tracking calibration dates and results for medical test equipment. Administrative record keeping.

[Assistant] Content: Work instructions for the CalibrationTracker Equipment Logger are codified in SOPs maintained within the ISO 13485 quality management system. SOP-010 (development planning), SOP-011 (risk management), SOP-012 (configuration management), and SOP-013 (verification) define step-by-step procedures for each IEC 62304 lifecycle activity applicable to the Calibration Record System.


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: Known anomalies in SOUP components used by the AllergyCard Patient Allergy Viewer are evaluated per Clause 7.1.3 against the specific usage context of the Patient Allergy Display. Each known anomaly is assessed for its potential to contribute to a hazardous situation, and risk control measures are implemented where the anomaly is relevant to Read-only display of patient allergy information at point of care.


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

[User]
Write a FMEA section on documenting failure modes and their effects for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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


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

[User]
Expand requirement SRS-DATA-002: "data retention period" (Category: data)
Project: ECGInsight Rhythm Interpreter | ECG Interpretation Service | Class B
Automated preliminary interpretation of 12-lead ECG recordings for physician review and overread. Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

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

[Assistant]
Description: Data retention in the ECGInsight Rhythm Interpreter shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the ECG Interpretation Service.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


[System] You are an IEC 62304 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 NeuroStim Programmer (neurostimulator programmer, Class C):

"Verification activities follow IEC 62304 Clause 4.5 for security testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 4.5 which does not exist. Clause 4 only has 4.1, 4.2, 4.3. The reference must be corrected to a valid clause number.


[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: "data acquisition from conductivity probe" (Category: functional)
Project: WaterPure Quality Logger | Water Quality Data Logger | Class A
Continuous logging of purified water parameters for GMP compliance. Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

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

[Assistant]
Description: The WaterPure Quality Logger shall continuously sample conductivity probe data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Water Quality Data Logger.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 7.1.1.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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


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

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

"The development plan references IEC 62304 Clause 5.4.5 and Clause 10.1 for the PhysioTrack Rehab."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.4.5 and 10.1, neither of which exists. Clause 5.4 has 5.4.1 through 5.4.4 only. IEC 62304 has no Clause 10. Standard ends at Clause 9. All clause references must be corrected.


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

[User]
Write a SDP section on configuration identification approach for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clauses 8.1, 8.1.1.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: Configuration items for the DoseLog Radiation Badge Reader Dosimetry Data Logger are identified and placed under version control per Clause 8.1. The configuration baseline includes all items needed to reproduce the released software: source code, build scripts, third-party libraries, and the documentation set.


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

[User]
Write a SRS section on sensor and communication protocol requirements for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clause 5.2.2.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: Interface requirements for the NeoFeed Neonatal Feeding Pump specify the communication protocols, data formats, and timing constraints for each external interface of the Neonatal Feeding Pump Firmware. The primary data acquisition interface uses stepper motor driver with specified data rates and error detection mechanisms.


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

[User]
Write a SDP section on milestones and phase transition criteria for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clause 5.1.1.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Milestones governing the InhaleSense Smart Inhaler Tracker lifecycle include Requirements Baseline, Architecture Baseline, Implementation Complete, Verification Complete, and Release Readiness. Each milestone has defined entry and exit criteria documented in this plan. No milestone can be declared complete while open problem reports of severity "major" or higher remain unresolved.


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

"Verification activities follow IEC 62304 Clause 5.6.8 for deployment validation."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.6.8 which does not exist. Clause 5.6 has 5.6.1 through 5.6.7 only. The reference must be corrected to a valid clause number.


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

[User]
Write a FMEA section on FMEA scope for Class C -- comprehensive analysis for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clause 7.1.1.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: The NeoFeed Neonatal Feeding Pump FMEA per Clause 7.1.1 provides exhaustive coverage of every software function in the Neonatal Feeding Pump Firmware that could contribute to a hazardous situation. Each function is analyzed for failure modes including incorrect output, missing output, untimely output, and unexpected output. Risk priority numbers drive verification and risk control priorities.


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

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

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


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

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

"The PhysioTrack Rehab development environment is configured following best practices. Tools are selected as appropriate for the project requirements."

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


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

[User]
Expand requirement SRS-DATA-002: "record keeping duration" (Category: data)
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 RadOnco Cloud Treatment Planner shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Cloud Radiation Treatment Planning SaMD.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Expand requirement SRS-DATA-001: "data retention period" (Category: data)
Project: HomeVent BiPAP Controller | BiPAP Device Firmware | Class C
Home bilevel ventilatory support with auto-titrating pressure and leak compensation. Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

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

[Assistant]
Description: Data retention in the HomeVent BiPAP Controller shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the BiPAP Device Firmware.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


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

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

"REQ-SRS-045: The HydroLog software shall provide a mechanism to export all configuration parameters to a structured file format. The export shall include version metadata. Acceptance criterion: exported file can be parsed and all parameters match the current configuration. Priority: Desirable. Source: User need."

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


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

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

"An independent verification and validation (IV&V) team reviews all CaloriePal development artifacts and test results before release approval."

[Assistant]
Verdict: FAIL
Note: Content mandates independent verification and validation (IV&V) for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent verification is required only for Class C.


[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 purpose and scope for Class A with minimal documentation for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clause 5.1.1.
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 scope of this plan covers the full software lifecycle of the InhaleSense Smart Inhaler Tracker, a Smart Inhaler Adherence Tracker classified as Safety Class A under IEC 62304 Clause 4.3. Because the software cannot contribute to a hazardous situation, the plan omits detailed design documentation (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6), concentrating instead on system-level activities that confirm the Smart Inhaler Adherence Tracker meets its specified requirements.


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

[User]
Write a SRS section on latency and throughput requirements for GaitSense Walking Analysis, a Class B Gait Analysis Insole Firmware. Reference IEC 62304 Clause 5.2.2.
Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

[Assistant] Content: Timing requirements for the GaitSense Walking Analysis include end-to-end latency from sensor acquisition to display update, processing throughput for sustained data streams, and startup time. Each timing requirement has a specific numeric bound and is verified through system testing of the Gait Analysis Insole 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 BloodBank Manager (blood bank inventory system, Class A):

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

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


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

[User]
Expand requirement SRS-SAFE-001: "fault response and safe shutdown" (Category: safety)
Project: DoseVerify In-Vivo Dosimetry System | In-Vivo Dosimetry Verification Software | Class C
Real-time verification of delivered radiation dose using in-vivo dosimeter measurements during treatment. Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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 detection of a critical software fault, the DoseVerify In-Vivo Dosimetry System shall transition to its defined safe state within the specified time, disabling any active output that could contribute to harm.
Rationale: A deterministic safe-state transition prevents the In-Vivo Dosimetry Verification Software from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: All 20 defined fault scenarios result in correct safe-state entry within timing limits across 10 iterations each.
Source: Risk control


[System] You are 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 NeuroStim Programmer (neurostimulator programmer, Class C):

"Architectural design follows IEC 62304:2022 Clause 5.3 for Class C devices."

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


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

[User]
Write a SDP section on risk control verification and traceability for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

[Assistant] Content: Risk control verification for the NutriCalc TPN Formulation Tool 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 TPN Formulation Calculator.


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

"For the NurseCall Hub, verification consists of executing system tests against the software requirements. Class A software does not require formal unit testing, integration testing, or independent verification. Test results are recorded per Clause 5.7.5 and any anomalies are handled through the problem resolution process per Clause 9."

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


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

[User]
Write a SRS section on data retention and integrity requirements for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: Data requirements for the RetinaStim Visual Prosthesis Controller specify retention periods, storage formats, and integrity controls for all persistent data managed by the Retinal Prosthesis Controller Firmware. Data integrity is ensured through checksums or cryptographic hashes, and corrupted data is detected before use in any processing function.


[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 detailed design per Clause 5.4 subdivides each software item into software units (Clause 5.4.1). Detailed design documents interfaces (Clause 5.4.3) and is verified per Clause 5.4.4 by reviewers independent of the author."

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


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

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

[Assistant] Content: This Software Requirements Specification defines the functional, performance, and interface requirements for the DermaAssist Skin Lesion Classifier Skin Lesion Classification App. Requirements are derived from system requirements, the risk management file, and stakeholder needs analysis per IEC 62304 Clause 5.2.1. Each requirement is uniquely identified, prioritized, and traceable to its source.


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

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

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

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


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

[User]
Write a TRACE section on gap identification and coverage analysis for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clause 5.7.4.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

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


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

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

"The lifecycle processes for the RetinaScan Pro comply with ISO 13485-2."

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


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

[User]
Write a SDP section on hazard identification for the specific device for SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

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


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

[User]
Expand requirement SRS-SAFE-001: "absence of safety-critical functions" (Category: safety)
Project: NutriView Food Diary | Nutritional Tracking Display App | Class A
Personal food logging and nutritional data visualization. Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

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

[Assistant]
Description: The Nutritional Tracking Display App software functions are limited to informational display and data presentation, with no capability to influence clinical decisions or therapeutic actions.
Rationale: The Class A classification of the Nutritional Tracking Display App depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Nutritional Tracking Display App.
Source: Regulatory


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

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clause 5.2.3.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

[Assistant] Content: Threat-to-mitigation traceability for the NutriCalc TPN Formulation Tool TPN Formulation Calculator is maintained per Clause 5.2.3. Each STRIDE threat is mapped to a security requirement, an implementation, and a verification test. This traceability ensures no identified threat lacks a corresponding software control.


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

[User]
Expand requirement SRS-FUNC-005: "measurement data archival" (Category: functional)
Project: PathSlide Digital Pathology Viewer | Digital Pathology Viewer | Class A
Display of digitized pathology slides for reference viewing. Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

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


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

[User]
Write a SDP section on tool qualification for Class B and C for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.1.4.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: Verification tools for the TriagePro Emergency Scoring App Emergency Department Triage SaMD are qualified per Clause 5.1.4. Qualification records document the tool name, version, intended use in the verification process, and evidence that the tool produces correct results. Tools whose output is not relied upon for verification decisions do not require qualification.


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

[User]
Expand requirement SRS-FUNC-005: "data logging and retrieval" (Category: functional)
Project: LinacControl Beam Delivery System | Linear Accelerator Control Software | Class C
Controlling radiation beam delivery including gantry position, collimator settings, and dose monitoring. Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

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 Linear Accelerator Control Software shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via real-time fieldbus.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Linear Accelerator Control Software.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

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

"The StepTrack addresses IEC 62304 Clause 4.5 (security testing) through formal review."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 4.5 which does not exist. Clause 4 only has 4.1, 4.2, 4.3. The reference must be corrected to a valid clause number.


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

[User]
Write a TRACE section on traceability scope including risk controls for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: The RadView DICOM Viewer traceability matrix extends beyond functional requirements to include risk control traceability per Clause 7.3.2. Each risk control measure implemented in the Medical Image Viewer software is traced from the ISO 14971 hazard through the software requirement to the verification test confirming its effectiveness.


[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: "fault response and safe shutdown" (Category: safety)
Project: PharmaSafe CDSS | Clinical Decision Support System | Class B
Real-time clinical decision support for medication safety including interaction checking and dose validation. Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

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

[Assistant]
Description: A deterministic safe-state transition shall be triggered by any detected critical fault condition in the PharmaSafe CDSS, with all active outputs brought to a known safe configuration.
Rationale: A deterministic safe-state transition prevents the Clinical Decision Support System from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: All 20 defined fault scenarios result in correct safe-state entry within timing limits across 10 iterations each.
Source: Risk control


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

[User]
Expand requirement SRS-PERF-002: "real-time performance requirement" (Category: performance)
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: End-to-end latency from pressure transducer data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Bounded processing latency ensures the Ambulatory Blood Pressure Monitor Firmware provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


[System] You are an IEC 62304 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 ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

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


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

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

"This Software Development Plan for the CardioPulse Monitor is prepared in compliance with IEC 62304:2006+AMD1:2015 and ISO 14971:2019. Usability engineering follows IEC 62366-1:2015+AMD1:2020."

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


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971-2" which is incorrect. ISO 14971 has no Part 2. ISO/TR 24971:2020 is a separate technical report. All references must be corrected.


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

[User]
Write a SRS section on latency and throughput requirements for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: Performance requirements for the RetinaStim Visual Prosthesis Controller specify maximum latencies, throughput rates, and resource consumption limits for the Retinal Prosthesis Controller Firmware operating on Custom FPGA + ARM Cortex-M7. Latency requirements define the maximum time from input event to output response for each critical processing path during Processing camera input and driving retinal implant electrode stimulation patterns for artificial vision.


[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 hazard identification for the specific device for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: Hazard identification for the PainRelief PCA Pump Controller per Clause 7.1.2 considers all software functions that could contribute to patient harm. Identified causes include incorrect syringe position encoder processing, loss of communication on motor driver, and failure to detect out-of-range conditions during Patient-controlled analgesic delivery with lockout intervals and cumulative dose limits.


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

[User]
Write a SDP section on tool qualification for Class B and C for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.1.4.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

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


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

[User]
Write a SDP section on development platform and build infrastructure for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.1.4.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: Development infrastructure for the WeightAlert Neonatal Scale includes a C (embedded) toolchain, automated build and test pipelines, and version control for all source and configuration files. The Neonatal Scale Firmware targets MSP430, and the build system produces identical outputs for a given source revision, supporting the reproducibility requirements of Clause 5.8.3.


[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 FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clause 5.2.2.
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 shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Cold Chain Temperature Logger must sustain from DS18B20 temperature sensor without data loss or processing backlog on ATmega328P.


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

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

"Software release criteria for the ArthroNav include completeness of all Class C deliverables (Clause 5.8.1), correct version identification (Clause 5.8.2), documented residual anomalies (Clause 5.8.4), and release approval by the quality representative."

[Assistant]
Verdict: PASS
Note: Content correctly specifies full Class C rigor. 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 format and interoperability requirements for WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clause 5.2.2.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: Data exchanged by the WasteTrack Biohazard Logger via REST API conforms to defined formats documented in this SRS. The Biohazard Waste Tracking App validates incoming data against the format specification and rejects malformed messages with a logged error. Output data formats are deterministic and reproducible.


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

[User]
Write a SRS section on operational context and user population for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: This section describes the operational context of the PainRelief PCA Pump Controller PCA Pump Controller Firmware. The system is intended for Patient-controlled analgesic delivery with lockout intervals and cumulative dose limits, operating on MSP432 (dual-core safety). Key interfaces include motor driver, nurse call interface, LCD. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

[User]
Write a SRS section on user interaction requirements for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clause 5.2.2.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

[Assistant] Content: The AssetTrack Equipment Inventory user interaction requirements define the observable behavior of the Equipment Inventory System from the user's perspective. Requirements are organized by use scenario and specify the information displayed, the timing of updates, and the user actions supported during Tracking location and status of medical equipment for inventory management.


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

[User]
Expand requirement SRS-PERF-003: "memory usage budget" (Category: performance)
Project: NeoVent Neonatal Ventilator | Neonatal Ventilator Firmware | Class C
Mechanical ventilatory support for neonatal patients with precise low-volume delivery. Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

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

[Assistant]
Description: The NeoVent Neonatal Ventilator memory footprint on ARM Cortex-R5 shall remain within specified limits under worst-case operational scenarios.
Rationale: Memory constraints are fixed by the ARM Cortex-R5 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 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):

"The OxyPure Controller development follows IEC 62304:2006+AMD1:2015 for the software lifecycle. Risk management is performed per ISO 14971:2019. The quality management system conforms to ISO 13485:2016."

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


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

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

"The development plan references IEC 62304 Clause 5.1.12 and Clause Annex B.3 for the HydroLog."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.1.12 and Annex B.3, neither of which exists. Clause 5.1 has 5.1.1 through 5.1.11 only. IEC 62304 annexes are not cited as requirements. All clause references must be corrected.


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

[User]
Write a SDP section on development methodology for Class B for InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clause 5.1.1.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: The InfuRate IV Flow Calculator follows a V-model lifecycle with iterative refinement, as the Class B classification requires architectural verification and integration testing that map naturally to the V-model's verification branches. Phase gates are established at Requirements Baseline, Architecture Review, Integration Test Complete, and System Test Complete, each requiring documented evidence before proceeding.


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

[User]
Write a FMEA section on failure mode identification approach for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: The failure mode identification for the LabStream LIS Middleware Laboratory Information Middleware per Clause 7.1.2 considers every processing step from input to output. Failure categories include data corruption, computation error, timing fault, and communication loss. Each failure mode is linked to its potential causes, including SOUP defects evaluated per Clause 7.1.3.


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

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

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

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


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

[User]
Write a SRS section on user interaction requirements for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.2.2.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: The VitalBoard Patient Summary user interaction requirements define the observable behavior of the Patient Summary Dashboard from the user's perspective. Requirements are organized by use scenario and specify the information displayed, the timing of updates, and the user actions supported during Read-only display of patient vital sign history for clinical reference.


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

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

"The DermaScan AI development follows IEC 62304:2006+AMD1:2015 for the software lifecycle. Risk management is performed per ISO 14971:2019. The quality management system conforms to ISO 13485:2016."

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


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

[User]
Write a SDP section on change control process for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clauses 8.2, 8.2.1.
Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

[Assistant] Content: No change to the SurgiPlan 3D Surgical Planner baseline is implemented without an approved change request per Clause 8.2. The approval process evaluates the change's impact on safety, regulatory compliance, and previously verified functionality. Post-implementation verification confirms the change was correctly applied per Clause 8.2.3.


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

[User]
Expand requirement SRS-DATA-003: "measurement data lifecycle" (Category: data)
Project: WaveReview EEG Archive Viewer | EEG Archive Viewer | Class A
Read-only playback and display of archived EEG recordings. Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

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


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.0 which does not exist. Clause 5 starts at 5.1. The reference must be corrected to a valid clause number.


[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: "absence of safety-critical functions" (Category: safety)
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: No software path in the AirSentry Urban Air Quality Station shall control therapeutic outputs, modify diagnostic results, or generate clinical alerts, confirming the validity of the Class A safety classification.
Rationale: Confirming the absence of safety-relevant functions validates the Class A classification under IEC 62304 Clause 4.3.
Priority: Mandatory
Acceptance Criterion: Code review confirms no software path exists that controls therapeutic outputs, modifies diagnostic results, or generates clinical alerts.
Source: Regulatory


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

[User]
Expand requirement SRS-PERF-001: "real-time performance requirement" (Category: performance)
Project: SterilLog Sterilization Record System | Sterilization Record Logger | Class A
Recording and archiving sterilization cycle parameters for regulatory compliance. Software logging sterilization cycle parameters from autoclaves. Records temperature, pressure, and time for compliance documentation.

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: Processing latency of the Sterilization Record Logger shall be bounded to ensure timely output that reflects current input conditions.
Rationale: Real-time performance is critical for the Sterilization Record Logger to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


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

[User]
Write a SDP section on milestones and phase transition criteria for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clause 5.1.1.
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 development schedule is anchored to formal milestones with documented transition criteria. Progress is measured against these gates rather than calendar dates, ensuring the Laboratory Information Middleware meets all quality and safety requirements before advancing to the next lifecycle phase.


[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 operational context and user population for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 5.2.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: The GrowthChart Pediatric Viewer Growth Chart Display App is deployed in an environment where Visual display of pediatric growth measurements on standard percentile charts. Users include trained clinical staff and, where applicable, patients or caregivers. The Web SPA platform defines the computational environment, while FHIR Observation API provides the primary data communication pathway.


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

"REQ-SRS-056: Upon detecting a communication timeout with the sensor module, the ThermoGuard 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 SDP section on risk control verification and traceability for ChestAI Pulmonary Nodule Detector, a Class B AI Pulmonary Nodule Detection SaMD. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Cloud AI SaMD analyzing chest CT scans to detect and measure pulmonary nodules, providing CAD overlay for radiologist review. FDA De Novo pathway.

[Assistant] Content: Verification of risk controls for the ChestAI Pulmonary Nodule Detector follows Clause 7.3.1. Each control implemented in software has a corresponding test case that demonstrates the hazardous condition is mitigated. Traceability records per Clause 7.3.2 document the chain from hazard through requirement to verification evidence.


[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: "output refresh interval for BreathSync ICU Ventilator Controller" (Category: functional)
Project: BreathSync ICU Ventilator Controller | ICU Ventilator Controller Software | Class C
Automated mechanical ventilation with multiple modes, alarm management, and patient synchronization. Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

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 BreathSync ICU Ventilator Controller shall update the displayed values on the solenoid valve drivers at intervals no greater than the specified refresh period.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


[System] You are 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 GlucoTrack CGM (continuous glucose monitor display, Class B):

"SOUP management for the GlucoTrack CGM includes identification (Clause 8.1.2), functional specification (Clause 5.3.3), and anomaly list evaluation (Clause 7.1.3). SOUP items are version-controlled and changes are managed through the change control process (Clause 8.2)."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the GlucoTrack CGM (continuous glucose monitor display, Class B). 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 SOUP identification and management for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 8.1.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 SOUP register identifies every third-party component deployed in the Cloud ECG Analysis SaMD, including version, source, and functional role. Updates to SOUP items trigger re-evaluation of known anomalies per Clause 7.1.3 and regression testing proportional to the scope of change.


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

"Compliance with IEC 62304 Clause 11.1 (operational qualification) and Clause 4.4 (post-market surveillance) is demonstrated."

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


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

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

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

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


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

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

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

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


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

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

[Assistant] Content: Software-implemented risk controls for the RemotICU Continuous Monitoring Hub are documented as explicit requirements per Clause 5.2.3. Traceability from the ISO 14971 risk analysis through the SRS to verification test cases ensures that every risk control measure is implemented and verified in the Edge-to-Cloud ICU Monitoring Gateway.


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

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

[Assistant] Content: The Class B/C DialyFlow Dialysis Fluid Controller requires enhanced security controls beyond baseline requirements. The Hemodialysis Fluid Controller Firmware implements mutual authentication for all external interfaces, firmware integrity verification at startup, and secure update mechanisms. Vulnerability management follows IEC 81001-5-1:2021 throughout the product lifecycle.


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

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

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

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


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

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

[Assistant] Content: Processing requirements for the AllergyCard Patient Allergy Viewer Patient Allergy Display 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-PERF-002: "real-time performance requirement" (Category: performance)
Project: PathCloud AI Histology Analyzer | Cloud SaMD Histopathology Analysis Platform | Class B
AI-assisted identification of suspicious regions in digitized histology slides for pathologist review. Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

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

[Assistant]
Description: The PathCloud AI Histology Analyzer shall process acquired data and update the output within the specified end-to-end latency from sample acquisition to display update.
Rationale: Real-time performance is critical for the Cloud SaMD Histopathology Analysis Platform to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


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

"Architectural design follows IEC 62304:2020 Clause 5.3 for Class A devices."

[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 SDP section on hazard identification for the specific device for TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

[Assistant] Content: For the TeleRehab Remote Patient Monitor, potential software contributions to hazardous situations include IMU wearable data corruption, processing algorithm errors, and WebRTC communication failures. Each identified cause is evaluated for severity and probability, with risk control measures defined per Clause 7.2.1 and traced to software requirements.


[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 EchoAssist (echocardiogram analysis aid, Class B):

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

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


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

"MISRA C compliance and unit testing with MC/DC coverage are mandatory for the PillRemind."

[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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-006: "display update rate for Hand Dynamometer Firmware" (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: Output presentation on the BLE 5.0 shall refresh at the configured interval, reflecting the most recent processed data from the Hand Dynamometer Firmware pipeline.
Rationale: Display freshness is critical for the Hand Dynamometer Firmware to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
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 AutoDose TPN (total parenteral nutrition calculator, Class C):

"The AutoDose TPN problem resolution process follows Clause 9. Problem reports are prepared per Clause 9.1, investigated per Clause 9.2, and resolved through the change control process per Clause 9.4. Trends are analyzed per Clause 9.6."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the AutoDose TPN (total parenteral nutrition calculator, Class C). Standards references are accurate.


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

[User]
Write a SDP section on requirements elicitation and documentation for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

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


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

[User]
Write a SDP section on milestones and phase transition criteria for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clause 5.1.1.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

[Assistant] Content: The PressoTrack Blood Pressure Trending development schedule is anchored to formal milestones with documented transition criteria. Progress is measured against these gates rather than calendar dates, ensuring the Ambulatory Blood Pressure Monitor Firmware meets all quality and safety requirements before advancing to the next lifecycle phase.


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

[User]
Expand requirement SRS-DATA-001: "measurement record integrity" (Category: data)
Project: AnticoagCalc INR Dose Adjuster | Anticoagulation Dosing Support Tool | Class B
Suggesting warfarin dose adjustments based on INR values for physician review. Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

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

[Assistant]
Description: The AnticoagCalc INR Dose Adjuster shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Anticoagulation Dosing Support Tool are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


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

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

"The SleepWell software architecture per Clause 5.3 is decomposed to the unit level with detailed interface specifications for every inter-unit boundary."

[Assistant]
Verdict: FAIL
Note: Content mandates architectural decomposition per Clause 5.3 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.