[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 primary international standards applicable to development for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clause 5.1.2.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

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


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

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

"Compliance with IEC 62304 Clause 5.5.2.1 is demonstrated through user acceptance testing."

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


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

[User]
Write a SRS section on baseline security requirements for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.2.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: The WeightAlert Neonatal Scale Neonatal Scale Firmware implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

[User]
Write a SDP section on requirements verification approach for TriageAI Emergency Triage Assistant, a Class B ED Triage Decision Support App. Reference IEC 62304 Clause 5.2.6.
Tablet app assisting nurses in emergency department triage scoring based on vital signs and presenting symptoms.

[Assistant] Content: The TriageAI Emergency Triage Assistant requirements verification checklist per Clause 5.2.6 confirms: no ambiguous requirements, no untestable requirements, no contradictions between requirements, and complete traceability to system requirements and risk controls. The review is documented with reviewer names, findings, and disposition.


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

[Assistant] Content: The CogniTest Cognitive Assessment App development team follows company SOPs aligned with ISO 13485:2016 quality management requirements: SOP-010 governs software planning, SOP-012 governs configuration management, and SOP-013 governs verification. Each SOP is version-controlled and reviewed annually to maintain compliance.


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

[User]
Write a SDP section on requirements verification approach for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.2.6.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: Verification of HemaCount Digital Cell Counter software requirements follows Clause 5.2.6. Reviewers confirm that every requirement is complete, consistent, testable, and traceable. Requirements that implement risk controls are additionally verified against the ISO 14971 risk management file for the IVD Digital Cell Counter Software.


[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-003: "output precision and accuracy" (Category: performance)
Project: AnesBot Automated Anesthesia Controller | Automated Anesthesia Delivery Software | Class C
Target-controlled propofol infusion guided by processed EEG depth-of-anesthesia monitoring. Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

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

[Assistant]
Description: Output accuracy of the Automated Anesthesia Delivery Software shall meet or exceed the specified tolerance for all measurement parameters across operating conditions.
Rationale: Measurement accuracy directly affects clinical decisions based on the Automated Anesthesia Delivery Software output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Statistical analysis of 500 measurements shows mean error within tolerance and standard deviation within specified limits.
Source: Regulatory


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

[User]
Write a SDP section on hazard identification for the specific device for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The TrainCert Staff Certification Tracker risk analysis per Clause 7.1.2 identifies software causes of hazardous situations specific to the Training Certification System: 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-DATA-001: "record keeping duration" (Category: data)
Project: CardioRhythm ECG Analyzer | Single-Lead ECG Device Firmware | Class B
Acquisition and preliminary rhythm classification of single-lead ECG for clinical screening. Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay 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: Measurement records stored by the Single-Lead ECG Device Firmware shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Single-Lead ECG 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 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 PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clauses 8.2, 8.2.1.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

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


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

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

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

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


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

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

"REQ-SRS-078: The PhysioTrack Rehab shall maintain data integrity during concurrent access by multiple users. No data corruption or loss shall occur. Acceptance criterion: execute concurrent read/write operations and verify data consistency. Priority: Mandatory. Source: System requirement."

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


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

[User]
Write a TRACE section on traceability scope including risk controls for LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: Traceability scope for the LabStream LIS Middleware includes both functional requirements and risk control measures. Risk control traceability per Clause 7.3.2 links each hazard cause to the software control, the SRS requirement, the implementation, and the verification evidence for the Laboratory Information Middleware.


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clauses 5.7, 5.7.1.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

[Assistant] Content: Verification of the ScheduleSync Appointment Manager consists exclusively of system-level testing per IEC 62304 Clause 5.7. Test cases derive from the software requirements specification and exercise the Appointment Scheduling System end-to-end on the Web SPA platform. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are not required for Class A software and are excluded from the verification scope.


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

"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 NurseCall Hub (patient call system dashboard, Class A):

"System testing for the NurseCall Hub is conducted per Clause 5.7.1 through 5.7.5. Test procedures verify end-to-end functionality of the patient call system dashboard against approved requirements. Detailed design verification (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6) are excluded as not applicable to Class A."

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


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

[User]
Write a FMEA section on FMEA scope for Class C -- comprehensive analysis for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clause 7.1.1.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: Failure mode analysis for the Class C BreathSync ICU Ventilator Controller examines every software item in the ICU Ventilator Controller Software architecture for potential contributions to hazardous situations per Clause 7.1.1. The analysis assigns severity, probability, and detectability ratings to each failure mode. All failure modes with unacceptable risk have corresponding risk control measures traced to software 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 baseline security 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 Patient Summary Dashboard implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

[User]
Expand requirement SRS-FUNC-004: "device configuration management" (Category: functional)
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: Configuration changes to the DoseVerify In-Vivo Dosimetry System shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the In-Vivo Dosimetry Verification Software to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

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

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


[System] You are a regulatory 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 WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: Risk evaluation of SOUP in the WasteTrack Biohazard Logger follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Biohazard Waste Tracking App. Anomalies relevant to Logging and tracking biohazard waste container chain of custody are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

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

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

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


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

[User]
Write a SDP section on tool qualification for Class B and C for TriageAI Emergency Triage Assistant, a Class B ED Triage Decision Support App. Reference IEC 62304 Clause 5.1.4.
Tablet app assisting nurses in emergency department triage scoring based on vital signs and presenting symptoms.

[Assistant] Content: Tool qualification for the TriageAI Emergency Triage Assistant is performed for all tools whose output directly supports verification conclusions, per Clause 5.1.4. Qualified tools include the TypeScript/React build toolchain, code coverage analyzers, and the system test harness. Each tool's qualification record is maintained as a controlled document.


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

"System testing for the MedInventory verifies that all software requirements are met in the operational environment. Test failures trigger the software problem resolution process per Clause 9. No unit-level or integration-level tests are required for this Class A medical supply tracking system."

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


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

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

"Software unit acceptance criteria for the HydroLog include boundary value testing, equivalence partitioning, and error guessing per Clause 5.5.3."

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


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

[User]
Write a SAD section on architecture verification scope for ChestAI Pulmonary Nodule Detector, a Class B AI Pulmonary Nodule Detection SaMD. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
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: Architecture verification for the ChestAI Pulmonary Nodule Detector per Clause 5.3.6 confirms traceability from requirements to architectural elements, adequacy of interface definitions, and correct implementation of risk control measures in the AI Pulmonary Nodule Detection SaMD design.


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

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

"The test strategy for the ThermoGuard is limited to system-level verification. All requirements from the SRS are covered by system test cases per Clause 5.7.1. Test failures are managed through the software problem resolution process (Clause 9). Unit and integration testing are out of scope for this Class A 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 requirements verification approach for MindCalm Meditation Timer, a Class A Meditation Wellness App. Reference IEC 62304 Clause 5.2.6.
Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

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


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

[User]
Write a SRS section on resource constraints and scalability for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clause 5.2.2.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: Resource requirements for the WaveReview EEG Archive Viewer specify maximum memory utilization, persistent storage consumption, and processor loading on Windows/Linux desktop. The EEG Archive Viewer must operate within these constraints under worst-case conditions without degradation of safety-relevant functions.


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

[User]
Expand requirement SRS-SEC-002: "cryptographic data security" (Category: security)
Project: PulseRing Smart Ring Monitor | Wearable Smart Ring Firmware + Companion App | Class B
Continuous photoplethysmography-based heart rate and SpO2 monitoring via wearable ring with mobile companion. Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

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

[Assistant]
Description: All stored patient data in the Wearable Smart Ring Firmware + Companion App shall be protected by AES-256 or equivalent encryption, with keys managed per established cryptographic practices.
Rationale: Data-at-rest encryption is required to meet privacy regulations and protect patient confidentiality.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

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

"The BloodBank Manager addresses IEC 62304 Clause 7.5 for performance benchmarking and Clause 5.9 for continuous monitoring."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 7.5 and 5.9, neither of which exists. Clause 7 ends at 7.4. Clause 5 ends at 5.8. All clause references must be corrected.


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-001: "device configuration management" (Category: functional)
Project: InhaleSense Smart Inhaler Tracker | Smart Inhaler Adherence Tracker | Class A
Detecting inhaler actuation events and tracking medication adherence for asthma management. Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

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

[Assistant]
Description: Configuration changes to the InhaleSense Smart Inhaler Tracker shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Configurable parameters allow the Smart Inhaler Adherence Tracker to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User]
Write a SDP section on development methodology for Class A for StepSync Activity Tracker, a Class A Wellness Activity Display App. Reference IEC 62304 Clause 5.1.1.
Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

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


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

[User]
Write a SAD section on SOUP component integration and requirements for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Third-party software components used in the OBDView Diagnostic Display are documented per Clause 5.3.3, including functional and performance requirements imposed on each SOUP item. Hardware and software dependencies per Clause 5.3.4 are recorded to ensure that the Android environment satisfies all SOUP prerequisites.


[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 BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clause 5.1.4.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: The BalanceBoard Vestibular Trainer is developed in C++ (embedded) targeting the STM32H7 + display platform. Source code is maintained under version control with branching and tagging conventions defined in SOP-012. Build automation ensures reproducible compilation, and all toolchain versions are recorded as part of the configuration management baseline.


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

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

[Assistant] Content: The PulmoCheck Spirometry Analyzer Spirometry Analysis Software implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

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

"The DialysisGuard 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 DialysisGuard (hemodialysis machine controller, Class C). Standards references are accurate.


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

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

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

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


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

[User]
Write a FMEA section on risk control verification for DreamLog Sleep Monitor, a Class A Sleep Tracking Display App. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

[Assistant] Content: Verification of risk control measures for the DreamLog Sleep Monitor follows Clause 7.3.1. Each software-implemented control is tested to demonstrate that the hazardous condition is mitigated to an acceptable level. Verification results per Clause 7.3.3 are documented in the risk management file for the Sleep Tracking Display App.


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

[User]
Expand requirement SRS-SEC-001: "user identity verification" (Category: security)
Project: FetalGuard Heart Rate Monitor | Fetal Heart Rate Monitor Firmware | Class B
Continuous external fetal heart rate monitoring during labor with clinical display. External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the FetalGuard Heart Rate Monitor, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the Fetal Heart Rate Monitor Firmware operating parameters.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


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

[User]
Expand requirement SRS-SAFE-001: "Class A scope validation" (Category: safety)
Project: SeismicWatch Earthquake Early Warning | Seismic Early Warning Firmware | Class A
Detecting seismic P-waves and providing early warning of potentially damaging earthquakes. Firmware for a network of MEMS accelerometers providing earthquake early warning by detecting P-waves and estimating magnitude.

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 SeismicWatch Earthquake Early Warning software shall not implement any function that could directly control a therapeutic output, modify a diagnostic conclusion, or trigger a clinical alert, consistent with its Class A classification.
Rationale: The Class A classification of the Seismic Early Warning Firmware 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 Seismic Early Warning Firmware.
Source: Regulatory


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

[User]
Write a SDP section on safety classification process and documentation for PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clause 4.3.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

[Assistant] Content: Software safety classification for the PainScale Digital Assessment Tool follows the procedure defined in IEC 62304 Clause 4.3. The classification considers whether the Pain Assessment Tool can contribute to a hazardous situation and, if so, whether external risk controls reduce the severity to non-serious injury. The result directly determines which IEC 62304 lifecycle activities are mandatory.


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

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

"Architectural design follows IEC 62304-6 Clause 5.3 for Class C devices."

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


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

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

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

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


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

"Per IEC 62304, software safety classification is performed. Per IEC 62304, the safety class is determined. Per IEC 62304, the safety classification is documented. Per IEC 62304, the HydroLog is classified per IEC 62304."

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


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

[User]
Write a TRACE section on gap identification and coverage analysis for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clause 5.7.4.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

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


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

[User]
Write a SAD section on data paths and processing pipeline for ChemoFlow Infusion Controller, a Class C Chemotherapy Infusion Pump Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

[Assistant] Content: The ChemoFlow Infusion Controller data flow begins at the drop counting sensor interface and terminates at the user-facing output. Intermediate processing stages -- including validation, filtering, and computation -- are implemented as separate software items with defined interfaces per Clause 5.3.2. The Chemotherapy Infusion Pump Firmware data flow is documented to support traceability and integration testing.


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

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 5.2.3.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: Threat-to-mitigation traceability for the AnticoagCalc INR Dose Adjuster Anticoagulation Dosing Support Tool 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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on Class B classification justification and implications for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clause 4.3.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: The PathCloud AI Histology Analyzer receives a Class B safety classification per IEC 62304 Clause 4.3 because the Cloud SaMD Histopathology Analysis Platform can contribute to a hazardous situation, but external risk controls -- including clinician oversight and independent hardware safety mechanisms -- prevent the hazard from resulting in serious injury. Lifecycle activities required at Class B include architectural design (Clause 5.3), integration testing (Clause 5.6), and system testing (Clause 5.7).


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

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

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

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


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

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

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


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

[User]
Expand requirement SRS-FUNC-001: "continuous data sampling from USB webcam" (Category: functional)
Project: PostureGuard Desk Monitor | Posture Wellness Display Software | Class A
Visual feedback on desk posture for personal wellness awareness. USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

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

[Assistant]
Description: Data from the USB webcam shall be acquired by the PostureGuard Desk Monitor at the configured rate, with each sample timestamped and queued for processing.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Posture Wellness Display Software.
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 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"Software maintenance is planned. Software maintenance activities are defined. The maintenance plan covers all aspects. Maintenance follows the plan. The HeartLink maintenance is documented. Maintenance is performed."

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


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

"REQ-SRS-045: The AutoDose TPN 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 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 architectural overview for Class B for PhysioTrack Rehabilitation Monitor, a Class B Physical Therapy Tracking System. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

[Assistant] Content: The PhysioTrack Rehabilitation Monitor architecture follows a layered design separating IMU (accelerometer + gyroscope) data acquisition from processing logic and BLE 5.0 interface presentation. This decomposition isolates safety-relevant signal processing from non-critical display functions, supporting the Class B verification strategy of targeted integration testing at layer boundaries.


[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 fault tree analysis identifies root causes of potential software failures. Control measures include watchdog timers, redundant calculations, and plausibility checks on sensor data. Each measure is a traceable software requirement verified during system testing."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PhysioTrack Rehab (rehabilitation tracking system, Class B). 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 TRACE section on traceability scope including risk controls for FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: The FactoryTemp Industrial Temperature Monitor matrix traces two categories per Clause 5.7.1 and Clause 7.3.2: functional requirements (from system specification through design to test) and risk control requirements (from hazard analysis through SRS to verification). Both categories must show complete coverage before release of the Industrial Temperature Monitoring Firmware.


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

[User]
Write a FMEA section on risk control measures and implementation for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
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 risk controls per Clause 7.2.1 address each failure mode with unacceptable residual risk. Software-implemented controls per Clause 7.2.2 include defensive coding measures, plausibility checks, and safe-state transitions. Each control is documented as a software requirement and verified for the Ambulatory Blood Pressure Monitor Firmware.


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

[User]
Expand requirement SRS-SEC-001: "authentication for configuration access" (Category: security)
Project: StepSync Activity Tracker | Wellness Activity Display App | Class A
Passive display of physical activity metrics for personal wellness tracking. Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the StepSync Activity Tracker, with credential validation before granting access.
Rationale: Unauthorized configuration changes to the Wellness Activity Display App could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


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

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

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

[Assistant]
Description: A power-on self-test shall validate primary sensor communication, memory integrity, and FHIR Observation API connectivity before the Growth Chart Display App transitions to its operational state.
Rationale: Startup verification prevents the Growth Chart Display App from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


[System] You are 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 PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clause 5.2.2.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: The PathCloud AI Histology Analyzer operates as a Cloud SaMD Histopathology Analysis Platform where AI-assisted identification of suspicious regions in digitized histology slides for pathologist review. The software interfaces with external data sources and communicates via REST API, DICOM import. The operational environment, user population, and regulatory context described here constrain the requirements that follow.


[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 AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clause 5.2.2.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: The AllergyCard Patient Allergy Viewer Patient Allergy Display data requirements address storage, integrity, and lifecycle management. All persistent data is validated on read, and write operations use atomic commit mechanisms to prevent partial updates during 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 BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: Failure mode documentation for the BalanceBoard Vestibular Trainer per Clause 7.1.4 captures the complete chain from cause to effect for each identified failure. The FMEA worksheet records the affected function, failure mode, potential causes, effects on the Balance Training Platform Firmware user, and current detection mechanisms.


[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 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 shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Water Quality Data Logger must sustain from conductivity probe without data loss or processing backlog on PLC with HMI.


[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, ISO 14971:2019 risk management is integrated with the IEC 62304 software lifecycle. Risk control measures identified in the risk analysis are incorporated as software requirements per Clause 5.2.3. The medical device risk analysis is re-evaluated per Clause 5.2.4 after requirements changes."

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


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

[User]
Expand requirement SRS-DATA-001: "measurement record integrity" (Category: data)
Project: VisitorPass Access Management | Visitor Management System | Class A
Visitor registration and temporary badge issuance for hospital access. Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

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 VisitorPass Access Management shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Visitor Management System are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

[User]
Write a SRS section on user interaction requirements for FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clause 5.2.2.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: User interaction requirements for the FleetTrack GPS Tracking Module define the input mechanisms, display elements, and feedback provided by the Fleet GPS Tracking Firmware during Real-time GPS tracking and geofence monitoring of fleet vehicles. Requirements specify the information presented to the user, the actions available, and the system response to each user action.


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

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

"Standards compliance for the OxyPure Controller oxygen concentrator controller is established through IEC 62304:2006+AMD1:2015 (Clauses 5, 7, 8, 9), ISO 14971:2019 (all clauses), and ISO 13485:2016 (Clause 7.3 design controls). All citations reference the current editions."

[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 requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-FUNC-001: "device configuration management" (Category: functional)
Project: NutriCalc TPN Formulation Tool | TPN Formulation Calculator | Class B
Calculating TPN component concentrations and volumes based on nutritional requirements. Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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

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


[System] You are 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 LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clause 5.2.2.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: Interface requirements for the LinacControl Beam Delivery System specify the communication protocols, data formats, and timing constraints for each external interface of the Linear Accelerator Control Software. The primary data acquisition interface uses real-time fieldbus 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 SRS section on purpose of the SRS document for LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clause 5.2.1.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: This Software Requirements Specification defines the functional, performance, and interface requirements for the LinacControl Beam Delivery System Linear Accelerator Control Software. 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 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 DreamLog Sleep Monitor, a Class A Sleep Tracking Display App. Reference IEC 62304 Clause 5.2.2.
Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

[Assistant] Content: The DreamLog Sleep Monitor data requirements define how the Sleep Tracking Display App stores, retrieves, and protects data acquired during Visualizing sleep quality data for personal wellness awareness. Requirements specify data format, retention duration, backup frequency, and the behavior when data corruption is detected.


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

[User]
Write a TRACE section on risk control coverage verification for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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


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

[User]
Write a SDP section on risk management integration into the lifecycle for HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clauses 7.1, 7.1.1.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

[Assistant] Content: The HandGrip Strength Dynamometer risk management process is concurrent with development, not sequential. Software causes of hazardous situations are identified per Clause 7.1 and documented per Clause 7.1.4. Risk controls are implemented as software requirements and verified through the applicable testing levels for the Hand Dynamometer 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):

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

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


[System] You are 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 purpose of the architecture document for AnesBot Automated Anesthesia Controller, a Class C Automated Anesthesia Delivery Software. Reference IEC 62304 Clause 5.3.1.
Software controlling target-controlled infusion of propofol based on BIS monitoring. Overdose could cause respiratory arrest.

[Assistant] Content: The AnesBot Automated Anesthesia Controller Software Architecture Document establishes the high-level design structure of the Automated Anesthesia Delivery Software per Clause 5.3.1. It defines the decomposition into software items, their interfaces, and the rationale for design decisions including technology choices and architectural patterns on QNX RTOS on ARM.


[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 test records and acceptance criteria for Class B for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clauses 5.6.7, 5.7.5.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: The GlucoSpot Continuous Glucose Display verification records comprise integration test results (Clause 5.6.7) and system test results (Clause 5.7.5). Pass criteria require every architectural interface exercised by at least one integration test and every SRS requirement covered by at least one system test. Anomalies are tracked in the problem resolution process per Clause 9.1.


[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: RemotICU Continuous Monitoring Hub | Edge-to-Cloud ICU Monitoring Gateway | Class B
Aggregating bedside monitor data at the edge and streaming to cloud for tele-ICU clinical oversight. Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU 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: Measurement records stored by the Edge-to-Cloud ICU Monitoring Gateway shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Write a SRS section on data retention and integrity requirements for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clause 5.2.2.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: The PostureGuard Desk Monitor data requirements define how the Posture Wellness Display Software stores, retrieves, and protects data acquired during Visual feedback on desk posture for personal wellness awareness. Requirements specify data format, retention duration, backup frequency, and the behavior when data corruption is detected.


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

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

"The CaloriePal development team follows appropriate processes and procedures. Training is provided as needed to ensure competency in relevant areas."

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


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

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clause 5.2.3.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

[Assistant] Content: Each STRIDE threat identified for the PedDose Pediatric Dosing App maps to a security control requirement in the SRS per Clause 5.2.3. The Pediatric Dosing Calculator App threat-to-requirement traceability ensures that every identified threat is mitigated by a verifiable software control. Residual threats that cannot be fully mitigated in software are documented in the risk management file.


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

[User]
Expand requirement SRS-SAFE-001: "safety classification confirmation for Class A" (Category: safety)
Project: StepSync Activity Tracker | Wellness Activity Display App | Class A
Passive display of physical activity metrics for personal wellness tracking. Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

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

[Assistant]
Description: The StepSync Activity Tracker software shall not implement any function that could directly control a therapeutic output, modify a diagnostic conclusion, or trigger a clinical alert, consistent with its Class A classification.
Rationale: The Class A classification of the Wellness Activity 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 Wellness Activity Display App.
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 PacePilot (pacemaker programmer, Class C):

"The PacePilot addresses IEC 62304 Clause 4.5 for deployment validation and Clause 5.7.6 for post-market surveillance."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 4.5 and 5.7.6, neither of which exists. Clause 4 only has 4.1, 4.2, 4.3. Clause 5.7 has 5.7.1 through 5.7.5 only. All clause references must be corrected.


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

[User]
Expand requirement SRS-FUNC-004: "initialization integrity checks" (Category: functional)
Project: TriageAI Emergency Triage Assistant | ED Triage Decision Support App | Class B
Assisting emergency nurses with triage acuity scoring based on patient assessment data. Tablet app assisting nurses in emergency department triage scoring based on vital signs and presenting symptoms.

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

[Assistant]
Description: A power-on self-test shall validate primary sensor communication, memory integrity, and manual input connectivity before the ED Triage Decision Support App transitions to its operational state.
Rationale: A power-on self-test confirms hardware and software readiness before the ED Triage Decision Support App begins use.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

[User]
Write a SRS section on data retention and integrity requirements for RespiRate Respiratory Monitor, a Class B Respiratory Rate Monitor Firmware. Reference IEC 62304 Clause 5.2.2.
Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

[Assistant] Content: Persistent data managed by the RespiRate Respiratory Monitor includes configuration parameters, acquired measurements from bio-impedance electrodes, and operational logs. Data integrity requirements specify error detection mechanisms and the Respiratory Rate Monitor Firmware response to data corruption events.


[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: "initialization integrity checks" (Category: functional)
Project: PulmoCheck Spirometry Analyzer | Spirometry Analysis Software | Class B
Analysis and interpretation of spirometry test data with predicted value comparison. Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

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

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


[System] You are a regulatory 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 LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clause 8.1.2.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

[Assistant] Content: All software of unknown provenance used in the LabStream LIS Middleware is identified and documented per Clause 8.1.2. For each SOUP component, the name, version, manufacturer, and intended use within the Laboratory Information Middleware are recorded. Known anomaly lists for each SOUP item are evaluated during risk analysis per Clause 7.1.3.


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

[User]
Write a TRACE section on traceability scope including risk controls for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: Traceability for the BillingBridge Claims Processor Claims Processing Service covers all software requirements per Clause 5.7.1 and all software-implemented risk controls per Clause 7.3.2. The combined matrix provides a single view of verification completeness for functional and safety aspects.


[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 DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clause 5.1.2.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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


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

[User]
Write a SDP section on internal SOPs and procedures for PulmoCheck Spirometry Analyzer, a Class B Spirometry Analysis Software. Reference IEC 62304 Clause 5.1.2.
Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

[Assistant] Content: The PulmoCheck Spirometry Analyzer development team follows company SOPs aligned with ISO 13485:2016 quality management requirements: SOP-010 governs software planning, SOP-012 governs configuration management, and SOP-013 governs verification. Each SOP is version-controlled and reviewed annually to maintain compliance.


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

[User]
Expand requirement SRS-SEC-001: "authentication for configuration access" (Category: security)
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: Access to configuration and administrative functions of the Nutritional Tracking Display App shall be restricted to authenticated and authorized users.
Rationale: Access control prevents unauthorized modification of the Nutritional Tracking Display App operating parameters.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


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

[User]
Write a SDP section on milestones and phase transition criteria for GasMonitor Anesthetic Gas Logger, a Class A Anesthetic Gas Concentration Logger. Reference IEC 62304 Clause 5.1.1.
Software logging waste anesthetic gas concentrations in operating rooms for occupational safety compliance. Recording only.

[Assistant] Content: Phase transitions for the GasMonitor Anesthetic Gas Logger are gated by documented completion criteria. The Requirements Baseline requires verified, traceable software requirements. The Implementation Freeze requires all code reviewed and committed. The Release Readiness Review requires all verification records complete, all problem reports dispositioned, and the Anesthetic Gas Concentration Logger release package assembled.


[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 FetaSound (fetal heart rate monitor, Class B):

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

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


[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 requires structural coverage analysis including decision coverage for all modules."

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


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

[User]
Write a SRS section on system boundaries and external dependencies for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.2.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: System boundaries for the WeightAlert Neonatal Scale are defined at the software interface level. The Neonatal Scale Firmware receives input from load cell with 24-bit ADC and produces output via SPI. Components beyond these interfaces are outside the scope of this SRS and are addressed in system-level documentation.


[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 VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: The VisitorPass Access Management risk control traceability matrix per Clause 7.3.2 links every identified hazard cause to its software-implemented control and to the verification activity confirming its effectiveness. Clause 7.3.3 requires documentation of the verification results for each risk control measure applied to the Visitor Management System.