[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: PharmLog Medication History Viewer | Medication History Viewer | Class A
Read-only display of medication dispensing history. Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

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

[Assistant]
Description: Upon power-up, the PharmLog Medication History Viewer shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Medication History Viewer 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 milestones and phase transition criteria for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clause 5.1.1.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

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


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

[User]
Write a FMEA section on risk control measures and implementation for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

[Assistant] Content: Risk control measures for the DermaLens Teledermatology Platform are defined per Clause 7.2.1 and implemented in software per Clause 7.2.2. Controls include input validation for smartphone camera (via mobile app), range checking on processed values, and timeout detection on REST API. Each control is traced to a software requirement and verified through testing.


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

[User]
Write a THREAT section on threat model data flow decomposition for AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

[Assistant] Content: The AIDose Chemotherapy Decision Support threat model decomposes the Cloud AI Chemotherapy Dosing SaMD into data flow diagrams showing all external entities, processes, data stores, and data flows. Each data flow crossing a trust boundary is analyzed for threats. The decomposition covers sensor input, internal processing, and output via HL7 FHIR R4.


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

[User]
Write a SRS section on latency and throughput requirements for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.2.2.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: Timing requirements for the BeamPlan Radiation Treatment Planner include end-to-end latency from sensor acquisition to display update, processing throughput for sustained data streams, and startup time. Each timing requirement has a specific numeric bound and is verified through system testing of the Radiation Treatment Planning 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-SEC-001: "access control and authorization" (Category: security)
Project: LabView Results Portal | Laboratory Results Viewer | Class A
Read-only display of laboratory test results for clinician reference. Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

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 Laboratory Results Viewer shall be restricted to authenticated and authorized users.
Rationale: Access control prevents unauthorized modification of the Laboratory Results Viewer operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

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

"The HydroLog architecture identifies segregation necessary for risk control per Clause 5.3.5."

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


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

[User]
Write a SDP section on risk control requirements traceability for WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clause 5.2.3.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: Software-implemented risk controls for the WasteTrack Biohazard Logger are documented as explicit requirements per Clause 5.2.3. Traceability from the ISO 14971 risk analysis through the SRS to verification test cases ensures that every risk control measure is implemented and verified in the Biohazard Waste Tracking App.


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

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

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

[Assistant]
Description: The FallRisk Inpatient Assessment Tool shall operate within the specified RAM and flash memory budget on the Web SPA platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the Fall Risk Assessment App, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


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

[User]
Expand requirement SRS-PERF-003: "data processing timing constraint" (Category: performance)
Project: MedImage PACS Viewer | Web PACS Image Viewer | Class A
Web-based display and annotation of DICOM medical images for radiologist review. Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

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

[Assistant]
Description: Processing latency of the Web PACS Image Viewer shall be bounded to ensure timely output that reflects current input conditions.
Rationale: Real-time performance is critical for the Web PACS Image Viewer to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


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

"REQ-SRS-045: The PillRemind 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 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 BSACalc Body Surface Area Tool, a Class B BSA Calculator Web App. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

[Assistant] Content: SOUP components in the BSACalc Body Surface Area Tool are integrated through defined interfaces per Clause 5.3.3. For each component, the architecture specifies the functions used, the performance expectations, and the Web SPA requirements per Clause 5.3.4. SOUP anomaly evaluation per Clause 7.1.3 is documented in the risk management file.


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

"Software release for the BloodBank Manager follows Clause 5.8. Completeness is ensured per Clause 5.8.1, version identification per Clause 5.8.2, and known residual anomalies are documented per Clause 5.8.4 and evaluated per Clause 5.8.5."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the BloodBank Manager (blood bank inventory system, Class A). Standards references are accurate.


[System] You are a 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 HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clause 4.3.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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


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

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

"The CaloriePal architecture identifies segregation necessary for risk control per Clause 5.3.5."

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


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

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

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

[Assistant]
Description: Access to configuration and administrative functions of the Anticoagulation Dosing Support Tool shall be restricted to authenticated and authorized users.
Rationale: Unauthorized configuration changes to the Anticoagulation Dosing Support Tool 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. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on baseline security requirements for PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clause 5.2.2.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

[Assistant] Content: The PedDose Pediatric Dosing App security requirements cover confidentiality, integrity, and availability of the Pediatric Dosing Calculator App and its data per IEC 81001-5-1:2021. Requirements specify access control mechanisms, encryption for data at rest and in transit, session management, and audit logging.


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

[User]
Write a SDP section on lightweight review process for Class A for FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clause 5.1.1.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: Review of FactoryTemp Industrial Temperature Monitor Class A deliverables consists of a peer review by the project lead and a quality check by the QA representative. The review confirms completeness of the SDP, traceability of requirements, and adequacy of the system test plan. Independent technical review is not required for the Industrial Temperature Monitoring Firmware at this classification level.


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

[User]
Write a SRS section on functional requirements overview for AuditTrail QMS Event Logger, a Class A QMS Audit Trail Service. Reference IEC 62304 Clause 5.2.2.
Microservice capturing and storing quality management system audit events. Logging and reporting only.

[Assistant] Content: This section specifies the functional behavior of the AuditTrail QMS Event Logger QMS Audit Trail Service. Requirements cover data input from external sources, processing algorithms, output generation via REST API, and user interaction patterns. All functional requirements are derived from the system specification or risk analysis.


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

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

"Software safety classification is performed per IEC 62304-1 Clause 4.3."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-1" which is incorrect. IEC 62304 is a single-part standard. The correct citation is IEC 62304:2006+AMD1:2015. All references must be corrected.


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

[User]
Write a TRACE section on risk control coverage verification for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: The GrowthChart Pediatric Viewer gap analysis per Clause 5.7.4 and Clause 7.3.2 verifies that the risk control traceability chain is complete. Every hazard in the risk management file that has a software control must trace to a verified requirement in the Growth Chart Display App. Incomplete chains are flagged and resolved before release.


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

"SOUP is identified for the EchoAssist. SOUP anomaly lists are evaluated. SOUP is managed per the configuration management plan. SOUP items are documented. SOUP management follows IEC 62304."

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


[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 CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: The CardioCloud ECG Analysis Service Cloud ECG Analysis SaMD 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 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):

"All verification for the rehabilitation tracking system follows IEC 62304-2 requirements."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-2" which is incorrect. IEC 62304 has no Part 2. It is a single-part standard. 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 TRACE section on purpose and scope of the traceability matrix for DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clause 5.7.1.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: The DialyFlow Dialysis Fluid Controller traceability matrix provides end-to-end requirement coverage evidence per Clause 5.7.1. Every SRS requirement for the Hemodialysis Fluid Controller Firmware is traced to its implementing software item and to the verification test case(s) confirming correct implementation. Orphaned requirements and untested implementations are flagged for resolution.


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

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

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

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

[Assistant] Content: Requirements for the FridgeGuard Temperature Logger Cold Chain Temperature Logger are documented per Clause 5.2.2 with clear acceptance criteria enabling direct derivation of test cases. Each requirement traces backward to its source and forward to its verification activity in the traceability matrix.


[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 TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clause 5.2.1.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The SRS for the TrainCert Staff Certification Tracker documents every functional, performance, interface, and safety requirement governing the Training Certification System. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


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

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

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

[Assistant]
Description: The RetinaStim Visual Prosthesis Controller shall communicate with the miniature camera via RF coil to implant, implementing error detection and recovery for communication failures.
Rationale: Reliable sensor communication is the foundation of the Retinal Prosthesis Controller Firmware data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

[User]
Write a SRS section on functional requirements overview for 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: Functional requirements for the PulmoCheck Spirometry Analyzer specify the data processing, user interaction, and output generation capabilities of the Spirometry Analysis Software. Each requirement describes a discrete function the software shall perform during Analysis and interpretation of spirometry test data with predicted value comparison, with acceptance criteria sufficient to derive verification test cases.


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

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

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


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

[User]
Write a FMEA section on risk control verification for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

[Assistant] Content: Verification of risk control measures for the AssetTrack Equipment Inventory 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 Equipment Inventory System.


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

[User]
Expand requirement SRS-INTF-001: "primary sensor interface protocol" (Category: interface)
Project: WaveReview EEG Archive Viewer | EEG Archive Viewer | Class A
Read-only playback and display of archived EEG recordings. Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

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

[Assistant]
Description: The WaveReview EEG Archive Viewer shall communicate with the primary sensor via EDF/EDF+ file format, implementing error detection and recovery for communication failures.
Rationale: Reliable sensor communication is the foundation of the EEG Archive Viewer data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

[User]
Write a SAD section on architecture verification scope for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: The architecture described in this document is verified per Clause 5.3.6, confirming that all software requirements are addressed by at least one software item. Verification also confirms that the PaceSet Pacemaker Programmer Cardiac Pacemaker Programmer Software architecture supports the defined interfaces and does not introduce new hazards.


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

[Assistant] Content: Data flow decomposition for the BrachyDose HDR Afterloader Controller threat model identifies all pathways where data crosses trust boundaries in the HDR Brachytherapy Afterloader Firmware. Each crossing point -- input from external sensors, output to display systems, and communication with remote services via treatment console -- is analyzed for security threats.


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

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

[Assistant]
Description: The LabStream LIS Middleware shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "best practices" provide no project-specific information about the CardioPulse Monitor cardiac rhythm monitor. 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 SDP section on primary international standards applicable to development for ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clause 5.1.2.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

[Assistant] Content: Applicable standards for the ScheduleSync Appointment Manager include IEC 62304:2006+AMD1:2015 (software lifecycle), ISO 14971:2019 (risk management), ISO 13485:2016 (quality management), and IEC 62366-1:2015+AMD1:2020 (usability engineering). These standards collectively define the processes, documentation, and verification expectations for the Appointment Scheduling System.


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

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

"The lifecycle processes for the CardioPulse Monitor comply with IEC 62304-6."

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


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

[User]
Write a SDP section on SOUP identification and management for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clause 8.1.2.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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


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

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

"Each ThermoGuard unit undergoes boundary value analysis, equivalence class partitioning, and error guessing as part of unit verification per Clause 5.5."

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


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

[User]
Write a SRS section on resource constraints and scalability for GlucoEdge Continuous Glucose Platform, a Class B Hybrid CGM Edge-Cloud Platform. Reference IEC 62304 Clause 5.2.2.
Hybrid system: embedded BLE firmware on a wearable CGM patch streams readings to a phone app, which uploads to cloud for trend analysis and physician dashboard.

[Assistant] Content: Computational resource requirements for the GlucoEdge Continuous Glucose Platform define the maximum CPU utilization, RAM consumption, and flash/disk usage permitted on nRF52840 (firmware) + mobile + AWS Lambda. The Hybrid CGM Edge-Cloud Platform must meet all functional and timing requirements within these resource envelopes.


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

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

"The lifecycle processes for the DialysisGuard comply with IEC 14971."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 14971" which is incorrect. Wrong prefix. The correct standard is ISO 14971, not IEC 14971. All references must be corrected.


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

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

[Assistant] Content: This section specifies the functional behavior of the BalanceBoard Vestibular Trainer Balance Training Platform Firmware. Requirements cover data input from 4x load cells, processing algorithms, output generation via USB, and user interaction patterns. All functional requirements are derived from the system specification or risk analysis.


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

[User]
Expand requirement SRS-INTF-004: "primary sensor interface protocol" (Category: interface)
Project: ScreenFlow Population Health Screener | Serverless Population Health Screening SaMD | Class A
Processing population health screening questionnaires and generating risk-stratified follow-up recommendations. Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

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

[Assistant]
Description: Communication with the primary sensor over REST API shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Serverless Population Health Screening SaMD data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

[User]
Write a SDP section on milestones and phase transition criteria for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clause 5.1.1.
Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

[Assistant] Content: Transition between lifecycle phases requires completion of all phase-gate deliverables and sign-off by the designated reviewers. For the DermaAssist Skin Lesion Classifier project, key milestones include the Software Requirements Baseline (all requirements reviewed and traced to system requirements), the Design Freeze (architecture and interfaces finalized), and the Release Readiness Review (all verification complete and anomalies dispositioned).


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

[User]
Write a SDP section on development methodology for Class B for RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clause 5.1.1.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

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


[System] You are a 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: "data-at-rest encryption" (Category: security)
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: Patient-identifiable data stored by the PulmoCheck Spirometry Analyzer shall be encrypted at rest using a validated cryptographic algorithm with a key length of at least 256 bits.
Rationale: Encryption of stored patient data protects against unauthorized disclosure if the Spirometry Analysis Software storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

[User]
Write a SRS section on safety requirements for Class C -- comprehensive controls for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: Safety requirements for the Class C RadOnco Cloud Treatment Planner address all software contributions to hazardous situations that could result in serious injury or death. Controls include input data integrity checking with redundant validation, watchdog monitoring, safe-state transitions on fault detection, and alarm generation per Clause 5.2.3.


[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 system test execution and acceptance for Class A for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clauses 5.7, 5.7.4.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: Test completeness for the BillingBridge Claims Processor is measured by requirement coverage at the system level only, per Clause 5.7.4. Every requirement in the SRS is covered by at least one system test case executed on Cloud (AWS). The Claims Processing Service has no unit test or integration test deliverables, consistent with the Class A verification scope.


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

[User]
Write a SDP section on cybersecurity and health IT standards for HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clause 5.1.2.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: Information security for the HeartView Resting HR Display Heart Rate Display Firmware conforms to IEC 81001-5-1:2021, covering secure development practices, vulnerability disclosure, and post-market security monitoring. For devices incorporating electrical safety requirements, IEC 60601-1:2005+AMD2:2020 is referenced for programmable electrical medical system (PEMS) considerations.


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

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

"Risk control measures are implemented per ISO 62304 Clause 7."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 62304" which is incorrect. Wrong prefix. The correct standard is IEC 62304, not ISO 62304. 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 EchoAssist (echocardiogram analysis aid, Class B):

"Per IEC 62304, the EchoAssist software requirements are documented. Per IEC 62304, all requirements for the EchoAssist 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 EchoAssist.


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

[Assistant] Content: The HydroRemind Hydration Tracker communicates with external systems via e-ink display SPI. Requirements specify authentication, data encryption, message integrity verification, and timeout handling. The Hydration Tracking Firmware must continue safe operation if the external system is unavailable.


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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PacePilot (pacemaker programmer, Class C). 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 problem reporting and investigation for SeismicWatch Earthquake Early Warning, a Class A Seismic Early Warning Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Firmware for a network of MEMS accelerometers providing earthquake early warning by detecting P-waves and estimating magnitude.

[Assistant] Content: The SeismicWatch Earthquake Early Warning problem reporting process per Clause 9.1 captures all software anomalies with sufficient detail for reproduction and root cause investigation. Clause 9.2 investigation assesses whether the problem represents a safety risk, determines the affected scope within the Seismic Early Warning Firmware, and identifies the corrective action required.


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

[User]
Write a FMEA section on risk control measures and implementation for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: Each risk control for the TriagePro Emergency Scoring App per Clause 7.2.1 specifies the hazard addressed, the control mechanism, and the verification method. Controls implemented in software per Clause 7.2.2 are traced through the requirements-design-test chain to ensure complete implementation and verification in the Emergency Department Triage SaMD.


[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 StrokeAlert CT Perfusion Analyzer, a Class C AI Stroke Triage CT Perfusion SaMD. Reference IEC 62304 Clause 5.2.2.
Time-critical cloud SaMD processing CT perfusion scans to generate ischemic core and penumbra maps for acute stroke triage. Results pushed to mobile app within 5 minutes.

[Assistant] Content: Security requirements for the StrokeAlert CT Perfusion Analyzer address authentication, data protection, and access control for the AI Stroke Triage CT Perfusion SaMD. All persistent data is encrypted at rest, and data in transit over HL7 FHIR results uses transport layer encryption. Security requirements are aligned with IEC 81001-5-1:2021.


[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: "authentication for configuration access" (Category: security)
Project: ECGInsight Rhythm Interpreter | ECG Interpretation Service | Class B
Automated preliminary interpretation of 12-lead ECG recordings for physician review and overread. Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

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

[Assistant]
Description: The ECGInsight Rhythm Interpreter shall require authentication before allowing modification of device configuration parameters via DICOM ECG input.
Rationale: Unauthorized configuration changes to the ECG Interpretation Service could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

[User]
Expand requirement SRS-SEC-002: "access control and authorization" (Category: security)
Project: PressoTrack Blood Pressure Trending | Ambulatory Blood Pressure Monitor Firmware | Class B
Automated periodic blood pressure measurement and trending over 24 hours. Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the PressoTrack Blood Pressure Trending, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the Ambulatory Blood Pressure 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 a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"Code coverage analysis is mandatory for the MedInventory with minimum 85% line coverage."

[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 TRACE section on purpose and scope of the traceability matrix for ScreenFlow Population Health Screener, a Class A Serverless Population Health Screening SaMD. Reference IEC 62304 Clause 5.7.1.
Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

[Assistant] Content: The ScreenFlow Population Health Screener traceability matrix provides end-to-end requirement coverage evidence per Clause 5.7.1. Every SRS requirement for the Serverless Population Health Screening SaMD is traced to its implementing software item and to the verification test case(s) confirming correct implementation. Orphaned requirements and untested implementations are flagged for resolution.


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

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

"The lifecycle processes for the PacePilot comply with ISO 14971:2020."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971:2020" which is incorrect. No 2020 edition. Current: 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 SDP section on scope boundaries of the software system for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The TrainCert Staff Certification Tracker software boundary includes the application firmware, configuration data, and all SOUP components deployed on Web application. Hardware components, operating system kernels supplied by the platform vendor, and remote services accessed via email notifications are excluded from the software lifecycle activities defined here, though their influence on software behavior is addressed in the risk analysis.


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

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

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

[Assistant]
Description: The TempWatch Body Temperature Logger shall require authentication before allowing modification of device configuration parameters via I2C.
Rationale: Access control prevents unauthorized modification of the Temperature Logging Firmware operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

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

[Assistant] Content: The RadView DICOM Viewer software is classified as IEC 62304 Safety Class A because it cannot contribute to a hazardous situation. As a Medical Image Viewer used for Read-only display of medical images for reference viewing, the software provides informational output only and does not control any therapeutic function, deliver any treatment, or make any clinical decision that could cause harm if incorrect.


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

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

"Compliance with IEC 62304 Clause 5.5.6 (deployment validation) and Clause 5.10 (user acceptance testing) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.5.6 and 5.10, neither of which exists. Clause 5.5 has 5.5.1 through 5.5.5 only. Clause 5 ends at 5.8. All clause references must be corrected.


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

[User]
Write a SDP section on risk control requirements traceability for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clause 5.2.3.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: Clause 5.2.3 requires that risk control measures implemented in the DoseCalc Medication Calculator software appear as traceable requirements. The traceability chain runs from the ISO 14971 hazard analysis to the SRS requirement to the test case verifying the control's effectiveness in the Medication Dose Calculator App.


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

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

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

[User]
Write a SDP section on scope boundaries of the software system for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: This plan applies to all software executing within the WaveReview EEG Archive Viewer EEG Archive Viewer and its supporting build and verification infrastructure. External systems that exchange data with the EEG Archive Viewer via EDF/EDF+ file format are covered only at the interface boundary; their internal implementation is outside the scope of this SDP.


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

[User]
Write a SDP section on cybersecurity and health IT standards for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clause 5.1.2.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

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


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

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

"Release activities follow standard practices to ensure quality and traceability. The release package is prepared as needed for regulatory submission."

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


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

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

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

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


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

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

"The RadView DICOM software architecture is decomposed into units with detailed design specifications. Integration testing validates data flow between all units. Independent verification of all test results is mandatory."

[Assistant]
Verdict: FAIL
Note: Content mandates detailed design, integration testing, and independent verification for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Clauses 5.4, 5.6, and independent verification are not required for Class A.


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

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

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

[Assistant]
Description: The PhysioTrack Rehabilitation Monitor shall allow authorized users to configure operating parameters via BLE 5.0 and persist settings across power cycles.
Rationale: Parameter flexibility is essential for the Physical Therapy Tracking System 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 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: LinacControl Beam Delivery System | Linear Accelerator Control Software | Class C
Controlling radiation beam delivery including gantry position, collimator settings, and dose monitoring. Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

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

[Assistant]
Description: The LinacControl Beam Delivery System shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Linear Accelerator Control Software 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 SDP section on internal SOPs and procedures for AutoHUD Heads-Up Display Controller, a Class A Automotive HUD Controller Firmware. Reference IEC 62304 Clause 5.1.2.
Firmware rendering vehicle speed, navigation, and ADAS warnings on a windshield-projected heads-up display.

[Assistant] Content: Internal procedures governing AutoHUD Heads-Up Display Controller development include SOP-010 (Software Development Planning), SOP-011 (Risk Management Planning), SOP-012 (Configuration Management), and SOP-013 (Software Verification Planning). These standard operating procedures are maintained under the company's ISO 13485 quality management system and provide detailed work instructions for each lifecycle activity.


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

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

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


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

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

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

[Assistant]
Description: The ECGInsight Rhythm Interpreter shall communicate with the primary sensor via DICOM ECG input, implementing error detection and recovery for communication failures.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the ECG Interpretation Service output.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

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

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


[System] You are a 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: "stored data corruption detection" (Category: data)
Project: TempWatch Body Temperature Logger | Temperature Logging Firmware | Class A
Passive logging and display of skin temperature trends for personal interest. Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

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

[Assistant]
Description: Data integrity of all stored records in the Temperature Logging Firmware shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Temperature Logging Firmware 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 a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for ChestAI Pulmonary Nodule Detector, a Class B AI Pulmonary Nodule Detection SaMD. Reference IEC 62304 Clause 5.2.3.
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: Each STRIDE threat identified for the ChestAI Pulmonary Nodule Detector maps to a security control requirement in the SRS per Clause 5.2.3. The AI Pulmonary Nodule Detection SaMD 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 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: ThermoWatch Core Temperature Monitor | Core Temperature Monitor Firmware | Class B
Continuous core body temperature monitoring with trend display and threshold alerts. Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the ThermoWatch Core Temperature Monitor, with credential validation before granting access.
Rationale: Access control prevents unauthorized modification of the Core Temperature 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. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on primary international standards applicable to development for RoomBoard Digital Signage, a Class A Patient Room Digital Signage. Reference IEC 62304 Clause 5.1.2.
Hospital room digital signage displaying patient name, care team, and daily schedule. Display-only, no clinical data entry.

[Assistant] Content: Applicable standards for the RoomBoard Digital Signage include IEC 62304:2006+AMD1:2015 (software lifecycle), ISO 14971:2019 (risk management), ISO 13485:2016 (quality management), and IEC 62366-1:2015+AMD1:2020 (usability engineering). These standards collectively define the processes, documentation, and verification expectations for the Patient Room Digital Signage.


[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 InfuSafe Controller (insulin infusion pump controller, Class C):

"This plan references the following normative standards: IEC 62304:2006+AMD1:2015, ISO 14971:2019, ISO 13485:2016, and IEC 62366-1:2015+AMD1:2020. Each standard is cited with its correct edition year. The InfuSafe Controller development complies with all applicable clauses for Class C."

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


[System] You are 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: "measurement record integrity" (Category: data)
Project: FactoryTemp Industrial Temperature Monitor | Industrial Temperature Monitoring Firmware | Class A
Continuous monitoring and logging of factory floor temperatures for process control. Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

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

[Assistant]
Description: The FactoryTemp Industrial Temperature Monitor shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Industrial Temperature Monitoring Firmware 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 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: "display update rate for BSA Calculator Web App" (Category: functional)
Project: BSACalc Body Surface Area Tool | BSA Calculator Web App | Class B
Calculating body surface area for oncology dose determination. Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

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

[Assistant]
Description: Output presentation on the web form shall refresh at the configured interval, reflecting the most recent processed data from the BSA Calculator Web App pipeline.
Rationale: Display freshness is critical for the BSA Calculator Web App to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
Source: User need


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

[User]
Review this documentation excerpt for the FetaSound (fetal heart rate monitor, Class B):

"SOUP management follows applicable guidance and industry conventions. Third-party components are evaluated per best practices for the fetal heart rate monitor."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "best practices", "applicable guidance", "industry conventions" provide no project-specific information about the FetaSound fetal heart rate monitor. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

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

"This plan references the following normative standards: IEC 62304:2006+AMD1:2015, ISO 14971:2019, ISO 13485:2016, and IEC 62366-1:2015+AMD1:2020. Each standard is cited with its correct edition year. The HydroLog development complies with all applicable clauses for Class A."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; uses the correct IEC 62304 citation; correctly references ISO 14971:2019. Standards references are accurate.


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

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

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

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


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

[User]
Write a SDP section on requirements elicitation and documentation for IncidentReport Clinical Event Logger, a Class A Incident Reporting System. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

[Assistant] Content: Elicitation of requirements for the IncidentReport Clinical Event Logger follows Clause 5.2.1, drawing on system requirements, stakeholder interviews, and the risk management file. Requirements are documented with unique identifiers and classified by type: functional, performance, interface, or safety for the Incident Reporting System.