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

[Assistant] Content: Resource requirements for the LinacControl Beam Delivery System specify maximum memory utilization, persistent storage consumption, and processor loading on VxWorks RTOS on PowerPC. The Linear Accelerator Control Software must operate within these constraints under worst-case conditions without degradation of safety-relevant functions.


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

[User]
Write a SDP section on change control and trend analysis for problems for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clauses 9.4, 9.6.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: Problem resolution for the BillingBridge Claims Processor integrates with change control per Clause 9.4 -- every correction is implemented as a controlled change with impact assessment and regression testing. Trends per Clause 9.6 are evaluated quarterly and at release readiness to identify systemic quality issues in the Claims Processing Service.


[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 DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

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


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

[User]
Write a SRS section on data processing and transformation requirements for CardioLoop Cardiac Resync Controller, a Class C CRT Optimization Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware for cardiac resynchronization therapy devices optimizing biventricular pacing based on hemodynamic feedback.

[Assistant] Content: The CardioLoop Cardiac Resync Controller shall process data from intracardiac impedance and transform it into clinically meaningful output for Real-time optimization of biventricular pacing parameters based on hemodynamic sensor feedback. Data processing requirements specify input validation rules, algorithm accuracy tolerances, and output format constraints for the CRT Optimization Firmware.


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

[User]
Write a SDP section on requirements verification approach for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clause 5.2.6.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

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


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

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

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

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


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

[User]
Write a THREAT section on system description for threat modeling for ECGInsight Rhythm Interpreter, a Class B ECG Interpretation Service. Reference IEC 62304 Clause 5.2.1.
Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

[Assistant] Content: The ECGInsight Rhythm Interpreter threat model scope encompasses the ECG Interpretation Service, its communication interfaces (DICOM ECG input, HL7 results output, REST API), stored data, and the operational environment. Data flows between the input source and the application logic, and between the application and REST API are analyzed for potential 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-INTF-002: "sensor data link requirements" (Category: interface)
Project: PathCloud AI Histology Analyzer | Cloud SaMD Histopathology Analysis Platform | Class B
AI-assisted identification of suspicious regions in digitized histology slides for pathologist review. Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

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

[Assistant]
Description: The PathCloud AI Histology Analyzer shall communicate with the primary sensor via REST API, implementing error detection and recovery for communication failures.
Rationale: Reliable sensor communication is the foundation of the Cloud SaMD Histopathology Analysis Platform data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

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

"This plan is prepared in compliance with IEC 62304:2015 and ISO 13485:2016."

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


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

[User]
Write a SDP section on cybersecurity and health IT standards for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 5.1.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: Security controls for the GrowthChart Pediatric Viewer 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 Growth Chart Display App runs on general-purpose computing platforms outside the manufacturer's direct hardware control.


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

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

"For the RadBeam Planner, ISO 14971:2019 risk management is integrated with the IEC 62304 software lifecycle. Risk control measures identified in the risk analysis are incorporated as software requirements per Clause 5.2.3. The medical device risk analysis is re-evaluated per Clause 5.2.4 after requirements changes."

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


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

[User]
Write a SRS section on user interaction requirements for WoundTrack Healing Analyzer, a Class B Wound Assessment App. Reference IEC 62304 Clause 5.2.2.
Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

[Assistant] Content: The WoundTrack Healing Analyzer Wound Assessment App presents information to the user via camera API and accepts user input through defined interaction patterns. User interaction requirements are traceable to the usability engineering file per IEC 62366-1:2015+AMD1:2020.


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

[User]
Expand requirement SRS-INTF-002: "clinical system integration interface" (Category: interface)
Project: RadView DICOM Viewer | Medical Image Viewer | Class A
Read-only display of medical images for reference viewing. Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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 RadView DICOM Viewer shall exchange data with external systems via DICOM using the specified message format with error handling.
Rationale: External system connectivity is required for the Medical Image Viewer to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User]
Write a FMEA section on risk control measures and implementation for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: Each risk control for the DoseLog Radiation Badge Reader 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 Dosimetry Data Logger.


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

"The InfuSafe Controller Class C development lifecycle includes requirements analysis (Clause 5.2), architectural design (Clause 5.3), implementation, and multi-level verification. Integration testing per Clause 5.6 validates component interactions. System testing per Clause 5.7 verifies end-to-end functionality."

[Assistant]
Verdict: PASS
Note: Content correctly specifies full Class C rigor; limits verification to system testing per Clause 5.7. Standards references are accurate.


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

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

"The CardioPulse Monitor SOUP risk evaluation examines published anomaly lists per Clause 7.1.3. Known anomalies in third-party libraries are assessed for potential contribution to hazardous situations. Mitigations include version pinning, input validation, and fallback behavior when SOUP components fail."

[Assistant]
Verdict: PASS
Note: Content 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 RadBeam Planner (radiation therapy planning system, Class C):

"The RadBeam Planner software development plan addresses Clause 5.1 requirements. Planning includes risk management (Clause 5.1.7), documentation (Clause 5.1.8), and configuration management (Clause 5.1.9). The plan is kept updated per Clause 5.1.2."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the RadBeam Planner (radiation therapy planning system, 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 cybersecurity and health IT standards for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 5.1.2.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: Cybersecurity requirements for the SunGuard UV Index Display follow IEC 81001-5-1:2021 for health software and health IT systems security, addressing the full product lifecycle of the UV Exposure Display Firmware from design through decommissioning. Where the software is classified as health software running on general-purpose platforms, IEC 82304-1:2016 applies to the overall product safety.


[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: "computational accuracy requirement" (Category: performance)
Project: InsuPrecise Insulin Pump Controller | Insulin Pump Controller Firmware | Class C
Automated insulin delivery control with programmable basal rates and bolus calculations. Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

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: Computational results produced by the InsuPrecise Insulin Pump Controller shall be accurate to within the specified tolerance, validated against reference calculations.
Rationale: Measurement accuracy directly affects clinical decisions based on the Insulin Pump Controller Firmware output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
Source: Regulatory


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

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

"Software safety classification is performed per ISO 14971-2 Clause 4.3."

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


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

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

"IEC 62304 Clause 5.7.6 requires the NeuroStim Programmer to implement automated regression testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.7.6 which does not exist. Clause 5.7 has 5.7.1 through 5.7.5 only. The reference must be corrected to a valid clause number.


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

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

[Assistant]
Description: The WaterPure Quality Logger shall exchange data with external systems via 4-20mA analog using the specified message format with error handling.
Rationale: External system connectivity is required for the Water Quality Data Logger to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

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

"The PillRemind software development conforms to IEC 62311-1, with risk management per ISO 14971:2019."

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


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

[User]
Expand requirement SRS-PERF-002: "resource utilization limits" (Category: performance)
Project: FridgeGuard Temperature Logger | Cold Chain Temperature Logger | Class A
Continuous logging and display of storage temperatures for compliance documentation. Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

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 FridgeGuard Temperature Logger shall operate within the specified RAM and flash memory budget on the ATmega328P platform, including all runtime allocations.
Rationale: Memory constraints are fixed by the ATmega328P hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

[User]
Expand requirement SRS-INTF-002: "clinical system integration interface" (Category: interface)
Project: CalibrationTracker Equipment Logger | Calibration Record System | Class A
Tracking calibration schedules and recording calibration results for compliance. Web application tracking calibration dates and results for medical test equipment. Administrative record keeping.

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

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


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

"Each SleepWell module undergoes unit testing followed by integration testing. System testing validates end-to-end behavior. All results are independently reviewed."

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


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

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

"SOUP functional requirements for the ThermoGuard are specified per Clause 5.3.3."

[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 medical device regulatory standards expert with comprehensive knowledge of IEC 62304, ISO 14971, ISO 13485, IEC 62366-1, IEC 82304-1, IEC 81001-5-1, IEC 60601-1 and its sub-parts, and associated regulatory guidance. Provide accurate standards references. Never fabricate clause numbers or standard sub-parts.

[User] Does IEC 62304 have a Clause 10?

[Assistant]
No. IEC 62304:2006+AMD1:2015 contains Clauses 4 through 9 only:

- Clause 4: General requirements
- Clause 5: Software development process
- Clause 6: Software maintenance process
- Clause 7: Software risk management process
- Clause 8: Software configuration management process
- Clause 9: Software problem resolution process

There is no Clause 10, 11, or any higher-numbered clause.


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

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

"The development plan references IEC 62304 Clause 5.6.8 and Clause 5.0 for the PhysioTrack Rehab."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.6.8 and 5.0, neither of which exists. Clause 5.6 has 5.6.1 through 5.6.7 only. Clause 5 starts at 5.1. All clause references must be corrected.


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

[User]
Write a SDP section on requirements verification approach for HydroRemind Hydration Tracker, a Class A Hydration Tracking Firmware. Reference IEC 62304 Clause 5.2.6.
Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

[Assistant] Content: Software requirements are verified per Clause 5.2.6 through formal review confirming each requirement is unambiguous, testable, consistent with system requirements, and traceable to its source. The HydroRemind Hydration Tracker requirements baseline is frozen only after successful review by the designated reviewers.


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

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

"Architectural design follows IEC 62304-3 Clause 5.3 for Class A devices."

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-3" which is incorrect. IEC 62304 has no Part 3. 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 DermaScan AI (skin lesion classifier, Class B):

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

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


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

[User]
Write a SRS section on system boundaries and external dependencies for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clause 5.2.2.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: External dependencies of the TransVent Transport Ventilator include the STM32H7 operating environment, turbine flow sensor, and blower driver. The Transport Ventilator Firmware requirements assume these dependencies operate within their specified parameters; failure modes of external components are addressed in the 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 OxyPure Controller (oxygen concentrator controller, Class C):

"Compliance with IEC 62304 Clause Annex A.1 (operational qualification) and Clause 5.7.6 (performance benchmarking) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 5.7.6, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. Clause 5.7 has 5.7.1 through 5.7.5 only. All clause references must be corrected.


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

[User]
Write a SDP section on system test execution and acceptance for Class A for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 5.7, 5.7.4.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: Acceptance of the TrainCert Staff Certification Tracker is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Training Certification 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-DATA-002: "record keeping duration" (Category: data)
Project: SunGuard UV Index Display | UV Exposure Display Firmware | Class A
Passive display of UV index for personal awareness. Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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

[Assistant]
Description: Measurement records stored by the UV Exposure Display Firmware shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


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

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

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

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


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

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

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

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


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clause 7.1.1.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: This software FMEA for the MedRef Clinical Reference App is a simplified analysis appropriate for Class A software that cannot contribute to a hazardous situation. The analysis confirms that identified software failure modes -- including input data processing errors and REST API for DB sync rendering failures -- do not create patient safety risks, given the purely informational nature of the Clinical Drug Reference App output.


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

[User]
Expand requirement SRS-FUNC-005: "configuration persistence and validation" (Category: functional)
Project: ConsentView Informed Consent Archive | Consent Document Viewer | Class A
Read-only viewing of archived informed consent documents. Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

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

[Assistant]
Description: Operating parameters of the Consent Document Viewer shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Configurable parameters allow the Consent Document Viewer to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

[Assistant] Content: Interaction requirements for the RespiRate Respiratory Monitor specify all user-facing behaviors of the Respiratory Rate Monitor Firmware: screen layouts, navigation flows, alarm presentation (if applicable), and error messaging. Each interaction requirement includes the trigger condition, the expected system response, and the acceptance criteria for verification.


[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-023: The BloodBank Manager shall validate all input data against defined ranges before processing. Out-of-range values shall be rejected with an error code. Acceptance criterion: submit boundary values and verify correct acceptance/rejection. Priority: Mandatory. Source: Risk control."

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


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

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

[Assistant] Content: This plan establishes the development framework for the PulmoCheck Spirometry Analyzer Spirometry Analysis Software, scoped to the Class B activities mandated by IEC 62304. Integration testing per Clause 5.6 and system testing per Clause 5.7 constitute the primary verification gates. Unit testing is recommended for safety-relevant modules but is not a mandatory deliverable 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 data processing and transformation requirements for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clause 5.2.2.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

[Assistant] Content: The SurgLog Procedure Documentation App shall process data from tablet microphone and transform it into clinically meaningful output for Documentation and review of surgical procedure notes. Data processing requirements specify input validation rules, algorithm accuracy tolerances, and output format constraints for the Surgical Documentation App.


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

[User]
Write a SDP section on risk control requirements traceability for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clause 5.2.3.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

[Assistant] Content: Software-implemented risk controls for the SurgLog Procedure Documentation App 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 Surgical Documentation App.


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

[User]
Write a SDP section on minimal deliverables list for Class A for LabView Results Portal, a Class A Laboratory Results Viewer. Reference IEC 62304 Clause 5.1.8.
Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

[Assistant] Content: The LabView Results Portal Class A documentation plan produces five controlled documents: this SDP, the Software Requirements Specification, the System Test Plan and Report, the Software Release Record, and the Risk Management File. No additional verification documents are required for the Laboratory Results Viewer.


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

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

[Assistant] Content: This section describes the operational context of the AllergyCard Patient Allergy Viewer Patient Allergy Display. The system is intended for Read-only display of patient allergy information at point of care, operating on Web kiosk (Chrome kiosk mode). Key interfaces include HL7 FHIR AllergyIntolerance API. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

"Each NurseCall Hub module undergoes unit testing followed by integration testing. System testing validates end-to-end behavior. All results are independently reviewed."

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


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

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

"The BloodBank Manager development follows IEC 62304-6 for the software lifecycle."

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

[User]
Expand requirement SRS-DATA-001: "record keeping duration" (Category: data)
Project: GlucoEdge Continuous Glucose Platform | Hybrid CGM Edge-Cloud Platform | Class B
Continuous glucose monitoring with edge processing on wearable and cloud-based trend analysis for clinician review. 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.

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


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

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

"The development plan references IEC 62304 Clause Annex B.3 and Clause 5.5.2.1 for the ChemoCalc."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex B.3 and 5.5.2.1, neither of which exists. IEC 62304 annexes are not cited as requirements. IEC 62304 has no four-level numbering. All clause references must be corrected.


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

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

"The RetinaScan Pro development follows IEC 62304-4 for the software lifecycle."

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


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

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

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

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


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

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

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


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

[User]
Write a FMEA section on failure mode identification approach for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Software failure modes in the OBDView Diagnostic Display are identified using a structured approach per Clause 7.1.2: each software item is analyzed for what could go wrong (the failure mode), why it could go wrong (the cause), and what would happen (the effect). SOUP component anomalies per Clause 7.1.3 are included as potential failure causes.


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

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

"All BloodBank Manager software units shall undergo formal verification by an independent test team using white-box and black-box techniques."

[Assistant]
Verdict: FAIL
Note: Content mandates formal unit verification by independent test team for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Unit verification (Clause 5.5) and independent testing are not required for Class A.


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

[User]
Write a TRACE section on traceability scope including risk controls for PowerTrack UPS Monitor, a Class A UPS Monitoring Software. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

[Assistant] Content: Traceability scope for the PowerTrack UPS Monitor includes both functional requirements and risk control measures. Risk control traceability per Clause 7.3.2 links each hazard cause to the software control, the SRS requirement, the implementation, and the verification evidence for the UPS Monitoring Software.


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

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

[Assistant] Content: The RenalDose Renal Adjustment Calculator Renal Dose Adjustment Calculator is classified as Safety Class B under IEC 62304 Clause 4.3. Software malfunction could contribute to a hazardous situation, but independent risk controls external to the software prevent escalation to serious injury or death. The Class B designation requires architectural design verification (Clause 5.3.6), integration testing (Clause 5.6), and system testing (Clause 5.7).


[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 CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 5.7.1.
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 traceability matrix provides end-to-end requirement coverage evidence per Clause 5.7.1. Every SRS requirement for the Cloud ECG Analysis 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-001: "end-to-end processing latency" (Category: performance)
Project: WaterPure Quality Logger | Water Quality Data Logger | Class A
Continuous logging of purified water parameters for GMP compliance. Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

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

[Assistant]
Description: End-to-end latency from conductivity probe data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Real-time performance is critical for the Water Quality Data Logger 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-INTF-002: "sensor data link requirements" (Category: interface)
Project: WaterPure Quality Logger | Water Quality Data Logger | Class A
Continuous logging of purified water parameters for GMP compliance. Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

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

[Assistant]
Description: The WaterPure Quality Logger shall communicate with the conductivity probe via 4-20mA analog, implementing error detection and recovery for communication failures.
Rationale: Reliable sensor communication is the foundation of the Water Quality Data Logger data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Write a SDP section on problem reporting and investigation for SupplyChain Procurement Portal, a Class A Supply Chain Procurement System. Reference IEC 62304 Clauses 9.1, 9.2.
Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

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


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Risk evaluation of SOUP in the InhaleSense Smart Inhaler Tracker follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Smart Inhaler Adherence Tracker. Anomalies relevant to Detecting inhaler actuation events and tracking medication adherence for asthma management are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

[User]
Write a SRS section on requirements conventions and identification scheme for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: Requirements for the NeuroTune DBS Programmer Deep Brain Stimulator Programmer App 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 TRACE section on traceability scope including risk controls for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clauses 5.7.1, 7.3.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: The DermaLens Teledermatology Platform matrix traces two categories per Clause 5.7.1 and Clause 7.3.2: functional requirements (from system specification through design to test) and risk control requirements (from hazard analysis through SRS to verification). Both categories must show complete coverage before release of the Cloud Teledermatology SaMD.


[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: "alarm threshold management" (Category: functional)
Project: CardioCloud ECG Analysis Service | Cloud ECG Analysis SaMD | Class B
Automated arrhythmia detection and ECG interpretation as a cloud service for remote clinics. Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

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

[Assistant]
Description: The CardioCloud ECG Analysis Service shall generate audible and visual alarms within the specified response time when a monitored parameter exceeds its configured threshold.
Rationale: Timely alarm generation is essential for the Cloud ECG Analysis SaMD to alert clinicians to abnormal conditions requiring intervention.
Priority: Mandatory
Acceptance Criterion: Alarm triggers within the specified response time of a threshold crossing, measured over 50 test crossings with no false negatives.
Source: Risk control


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

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

"Verification activities follow IEC 62304 Clause Annex A.1 for user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause Annex A.1 which does not exist. IEC 62304 annexes are informative, not cited as requirements. The reference must be corrected to a valid clause number.


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

[User]
Write a SRS section on data processing and transformation requirements 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 data pipeline requirements specify end-to-end data flow from input acquisition through processing to output on HL7 FHIR R4. Requirements include input validation, range checking, unit conversion, and output formatting for AI-generated chemotherapy dose adjustment recommendations based on patient-specific pharmacogenomic and clinical data.


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

[User]
Expand requirement SRS-INTF-002: "external system data exchange" (Category: interface)
Project: CogniTest Cognitive Assessment App | Cognitive Assessment Application | Class B
Administering and scoring standardized cognitive screening tests for clinical neuropsychological assessment. Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

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

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


[System] You are a 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 ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

[Assistant] Content: The software system boundary for ClinTrial EDC Platform encompasses the Clinical Trial EDC Web Platform application and its direct interfaces: REST API, web application, CDISC ODM export. Components outside this boundary -- including external sensor hardware, manufacturing test fixtures, and third-party cloud services -- are addressed in the system-level risk analysis but are not governed by this plan.


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

"Architectural design follows ISO 14971-1 Clause 5.3 for Class A devices."

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


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

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

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


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

[User]
Write a SDP section on system test execution and acceptance for Class A for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clauses 5.7, 5.7.4.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

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


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

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

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


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

[User]
Write a SDP section on purpose and scope for Class B with moderate documentation for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clause 5.1.1.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: This plan establishes the development framework for the BalanceBoard Vestibular Trainer Balance Training Platform Firmware, scoped to the Class B activities mandated by IEC 62304. Integration testing per Clause 5.6 and system testing per Clause 5.7 constitute the primary verification gates. Unit testing is recommended for safety-relevant modules but is not a mandatory deliverable at this classification level.


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

[User]
Expand requirement SRS-FUNC-004: "data acquisition from primary sensor" (Category: functional)
Project: RenalDose Renal Adjustment Calculator | Renal Dose Adjustment Calculator | Class B
Calculating renal-adjusted medication doses based on estimated glomerular filtration rate. Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

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 RenalDose Renal Adjustment Calculator software shall acquire primary sensor data at the specified sampling rate and store values in a circular buffer for processing by the Renal Dose Adjustment Calculator signal pipeline.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Calculating renal-adjusted medication doses based on estimated glomerular filtration rate.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a SAD section on interface design between software items for PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clause 5.3.2.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Software item interfaces in the PharmaSafe CDSS architecture are specified per Clause 5.3.2 with sufficient detail to support independent implementation and verification. Each interface definition includes data format, timing constraints, and error handling contracts applicable to the Clinical Decision Support System.


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

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the StepTrack (wellness pedometer app, Class A). 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 NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: SOUP components in the NeoFeed Neonatal Feeding Pump are integrated through defined interfaces per Clause 5.3.3. For each component, the architecture specifies the functions used, the performance expectations, and the STM32L5 (TrustZone) requirements per Clause 5.3.4. SOUP anomaly evaluation per Clause 7.1.3 is documented in the risk management file.


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

[User]
Write a SDP section on risk control requirements traceability 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: Clause 5.2.3 requires that risk control measures implemented in the ChestAI Pulmonary Nodule Detector 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 AI Pulmonary Nodule Detection SaMD.


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

[User]
Write a SDP section on requirements verification approach for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clause 5.2.6.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Requirements verification for the OBDView Diagnostic Display is conducted per Clause 5.2.6 before the requirements baseline is established. The review confirms completeness, consistency, and testability. Any requirement failing these criteria is returned for rework before the Vehicle Diagnostic Display App proceeds to design.


[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 sensor and communication protocol requirements for ConsentView Informed Consent Archive, a Class A Consent Document Viewer. Reference IEC 62304 Clause 5.2.2.
Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

[Assistant] Content: Interface requirements for the ConsentView Informed Consent Archive specify the communication protocols, data formats, and timing constraints for each external interface of the Consent Document Viewer. The primary data acquisition interface uses REST API with specified data rates and error detection mechanisms.


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

[User]
Write a SDP section on risk control verification and traceability for VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

[Assistant] Content: Risk control measures in the VibeCheck Vibration Analyzer are verified per Clause 7.3.1 through the testing activities appropriate to the safety classification. Traceability per Clause 7.3.2 links each identified hazard to its risk control measure, the software requirement implementing the control, and the test case verifying the control's effectiveness in the Vibration Analysis Instrument Firmware.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 7.1.1.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: Failure mode analysis for the Class A GrowthChart Pediatric Viewer is a confirmatory exercise documenting that no identified failure mode of the Growth Chart Display App creates a hazardous situation. The analysis systematically considers data loss, incorrect computation, and display errors, confirming that Visual display of pediatric growth measurements on standard percentile charts remains safe even under worst-case software failure.


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

[User] What does IEC 82304-1 cover?

[Assistant] IEC 82304-1:2016 (Health software — General requirements for product safety) applies to standalone health software products (Software as a Medical Device / SaMD). It adds product-level safety requirements beyond the process requirements of IEC 62304. While IEC 62304 governs the software development process, IEC 82304-1 addresses the safety of the finished software product. Note: Part 1 exists; it covers general requirements.


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

[User]
Write a SAD section on data paths and processing pipeline for HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

[Assistant] Content: The processing pipeline of the HomeVent BiPAP Controller consists of sequential data transformations from raw input through processed output. Interface contracts per Clause 5.3.2 define the data format, timing, and error conditions at each pipeline stage boundary. The BiPAP Device Firmware architecture supports both streaming and batch processing modes where required.


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

[User]
Write a SDP section on risk management integration into the lifecycle for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clauses 7.1, 7.1.1.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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


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

[User]
Expand requirement SRS-DATA-002: "record keeping duration" (Category: data)
Project: BillingBridge Claims Processor | Claims Processing Service | Class A
Automated processing and submission of insurance claims. Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

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

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


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

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

[Assistant]
Description: Alarm thresholds shall be configurable per clinical protocol. The BreathSync ICU Ventilator Controller shall trigger alerts within the maximum allowable latency of a threshold crossing.
Rationale: Timely alarm generation is essential for the ICU Ventilator Controller Software to alert clinicians to abnormal conditions requiring intervention.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


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

[User]
Write a SDP section on risk control verification and traceability for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

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


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

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

"Software release for the WoundTrack 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 WoundTrack (wound measurement imaging system, Class B). Standards references are accurate.


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

[User]
Write a SDP section on comprehensive deliverables list for Class C for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clause 5.1.8.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

[Assistant] Content: The full Class C documentation set for the DoseVerify In-Vivo Dosimetry System includes: Software Development Plan, Software Requirements Specification, Software Architecture Document, Detailed Design Specification, Unit Test Plan and Report (with coverage metrics), Integration Test Plan and Report, System Test Plan and Report, Traceability Matrix, Risk Management File, and Software Release Record. Each deliverable undergoes independent review before approval.


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

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

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

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


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

[User]
Write a SDP section on problem reporting and investigation for HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

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


[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 HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: Risk control verification for the HeartView Resting HR Display per Clause 7.3.1 confirms that each control is correctly implemented and effective. Test cases exercise the control under normal and boundary conditions. Verification evidence per Clause 7.3.3 links the test result to the risk control measure and the originating hazard in the Heart Rate Display Firmware risk management file.


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

[User]
Write a FMEA section on risk control measures and implementation for PulseRing Smart Ring Monitor, a Class B Wearable Smart Ring Firmware + Companion App. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

[Assistant] Content: Risk control measures for the PulseRing Smart Ring Monitor Wearable Smart Ring Firmware + Companion App are prioritized per Clause 7.2.1: inherently safe design first, then protective measures in software, then information for safety. Software-implemented controls per Clause 7.2.2 are expressed as verifiable requirements and traced to their originating hazard.


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

[User]
Write a SDP section on SOUP identification and management for GlucoEdge Continuous Glucose Platform, a Class B Hybrid CGM Edge-Cloud Platform. Reference IEC 62304 Clause 8.1.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: Identification of SOUP for the GlucoEdge Continuous Glucose Platform follows Clause 8.1.2. Each SOUP component record includes title, version, supplier, intended function within the Hybrid CGM Edge-Cloud Platform, and a reference to the anomaly evaluation performed per Clause 7.1.3. SOUP updates are managed through the change control process per Clause 8.2.


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

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

"The InfuSafe Controller development follows IEC 62304-6 for the software lifecycle."

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


[System] You are a regulatory 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 user interaction requirements for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clause 5.2.2.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: The MedRef Clinical Reference App Clinical Drug Reference App presents information to the user via REST API for DB sync and accepts user input through defined interaction patterns. User interaction requirements are traceable to the usability engineering file per IEC 62366-1:2015+AMD1:2020.