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

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

"The AutoDose TPN development follows IEC 62304:2020 for the software lifecycle."

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


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

"Static analysis using MISRA C rules is mandatory for all SleepWell source files. Unit testing with MC/DC coverage is required for safety-critical paths."

[Assistant]
Verdict: FAIL
Note: Content mandates MISRA C static analysis and MC/DC unit testing for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). MISRA C and MC/DC coverage targets are Class C considerations, not required for Class A.


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

[User]
Expand requirement SRS-FUNC-003: "device configuration management" (Category: functional)
Project: AutoPancreas Closed-Loop Glucose Controller | Artificial Pancreas Controller Firmware | Class C
Automated closed-loop insulin delivery based on continuous glucose monitoring with predictive algorithms. Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

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 Artificial Pancreas Controller Firmware shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Parameter flexibility is essential for the Artificial Pancreas Controller Firmware to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

[Assistant] Content: Risk control measures for the PedDose Pediatric Dosing App are expressed as verifiable safety requirements per Clause 5.2.3. The Pediatric Dosing Calculator App implements defensive data processing, boundary condition detection, and communication timeout handling. Each safety requirement is verified through integration testing (Clause 5.6) or system testing (Clause 5.7).


[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 risk evaluation and anomaly management for RemotICU Continuous Monitoring Hub, a Class B Edge-to-Cloud ICU Monitoring Gateway. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

[Assistant] Content: Risk evaluation of SOUP in the RemotICU Continuous Monitoring Hub follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Edge-to-Cloud ICU Monitoring Gateway. Anomalies relevant to Aggregating bedside monitor data at the edge and streaming to cloud for tele-ICU clinical oversight are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

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

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

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


[System] You are a 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: IncidentReport Clinical Event Logger | Incident Reporting System | Class A
Submission and routing of clinical incident reports for quality review. Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

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 Incident Reporting System shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Incident Reporting System.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified 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 HeartLink (cardiac telemetry system, Class B):

"Risk management is performed. Risk analysis is conducted. Risk evaluation is completed. Risk control measures are implemented. Risk management activities are documented. The risk management process is followed."

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


[System] You are a regulatory 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 documenting failure modes and their effects for RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

[Assistant] Content: The RenalDose Renal Adjustment Calculator FMEA documents each failure mode per Clause 7.1.4, providing sufficient detail for risk evaluation: the software function affected, the failure mode, the cause(s), the effect on the Renal Dose Adjustment Calculator output, and the resulting hazard severity. This documentation is maintained in the risk management file.


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

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

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

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


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

"Verification planning for the StepTrack scopes testing to system level only, consistent with Class A requirements. The verification plan references Clause 5.7 and defines acceptance criteria for each software requirement. Code coverage analysis is not required and is not included in the plan."

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


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for PharmLog Medication History Viewer, a Class A Medication History Viewer. Reference IEC 62304 Clause 7.1.1.
Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

[Assistant] Content: This software FMEA for the PharmLog Medication History Viewer 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 FHIR MedicationDispense API rendering failures -- do not create patient safety risks, given the purely informational nature of the Medication History Viewer output.


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

"Software problem resolution follows ISO 14901 Clause 9."

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


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

[User]
Write a TRACE section on gap identification and coverage analysis for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clause 5.7.4.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: Gap analysis for the AnticoagCalc INR Dose Adjuster per Clause 5.7.4 examines the traceability matrix for completeness. Requirements without verification are flagged as critical gaps. Design elements without requirements are evaluated for removal or requirement creation. The Anticoagulation Dosing Support Tool cannot be released until all gaps are resolved.


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

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

"REQ-SRS-023: The EchoAssist 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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on change control process for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clauses 8.2, 8.2.1.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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


[System] You are 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 PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: Scope is limited to the PaceSet Pacemaker Programmer software items developed under this plan and released as a single configuration baseline. Peripherals, test jigs, and cloud infrastructure used during Programming and interrogating implanted cardiac pacemakers including rate settings, sensitivity, and output parameters are addressed by separate system-level documentation and are not governed by IEC 62304 Clause 5.1.1 activities described herein.


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

"Risk management is performed in accordance with applicable standards and regulatory expectations. Hazard analysis is conducted as required by the regulatory framework."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "applicable standards", "as required by" provide no project-specific information about the RadBeam Planner radiation therapy planning system. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

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

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

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


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

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

"The StepTrack integration test plan covers all inter-module interfaces per Clause 5.6."

[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 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 PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clause 5.2.6.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

[Assistant] Content: Verification of PressoTrack Blood Pressure Trending 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 Ambulatory Blood Pressure Monitor Firmware.


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

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

"Per Clause 5.4.2, each software unit of the StepTrack has detailed design documentation."

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


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

[User]
Expand requirement SRS-PERF-001: "output precision and accuracy" (Category: performance)
Project: TeleRehab Remote Patient Monitor | Remote Rehabilitation Platform | Class B
Remote physiotherapy monitoring with exercise tracking and therapist-patient video sessions. Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

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 TeleRehab Remote Patient Monitor shall maintain measurement accuracy within the specified tolerance across the full operating range of the IMU wearable.
Rationale: Inaccurate output from the Remote Rehabilitation Platform could lead to incorrect clinical actions, making accuracy a safety-critical requirement.
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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-001: "resource utilization limits" (Category: performance)
Project: DoseLog Radiation Badge Reader | Dosimetry Data Logger | Class A
Reading and archiving personal radiation exposure data from dosimeter badges. Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health 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 DoseLog Radiation Badge Reader shall operate within the specified RAM and flash memory budget on the Windows desktop platform, including all runtime allocations.
Rationale: Memory constraints are fixed by the Windows desktop hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


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

[User]
Write a SDP section on requirements elicitation and documentation for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: Software requirements for the GrowthChart Pediatric Viewer are derived from system requirements, the risk management file, and stakeholder inputs per Clause 5.2.1. Each requirement specifies functional behavior, performance criteria, or interface constraints relevant to the Growth Chart Display App and its use in Visual display of pediatric growth measurements on standard percentile charts.


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

[Assistant] Content: The PainRelief PCA Pump Controller problem correction workflow routes all fixes through the change control process per Clause 9.4. Trend analysis per Clause 9.6 reviews accumulated problem reports at each phase gate to detect recurring defect patterns, common root causes, and areas of the PCA Pump Controller Firmware requiring additional verification attention.


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

"All source code modules shall undergo unit testing using xUnit framework with coverage reporting."

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


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

[User]
Write a THREAT section on STRIDE threat categories applied to the device 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: Threats to the RespiRate Respiratory Monitor are categorized using the STRIDE framework: Spoofing of I2C AFE identity, Tampering with sensor data or configuration, Repudiation of clinical actions, Information Disclosure of patient data, Denial of Service disrupting Continuous respiratory rate monitoring with alarm generation for abnormal rates, and Elevation of Privilege through unauthorized parameter changes.


[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 BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: The processing pipeline of the BreathSync ICU Ventilator 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 ICU Ventilator Controller Software architecture supports both streaming and batch processing modes where required.


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for RespiRate Respiratory Monitor, a Class B Respiratory Rate Monitor Firmware. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Wearable firmware monitoring respiratory rate via chest impedance. Displays rate and alerts on bradypnea/tachypnea.

[Assistant] Content: Risk evaluation of SOUP in the RespiRate Respiratory Monitor follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Respiratory Rate Monitor Firmware. Anomalies relevant to Continuous respiratory rate monitoring with alarm generation for abnormal rates are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

[User]
Write a TRACE section on risk control coverage verification for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: Risk control coverage analysis for the ThermoWatch Core Temperature Monitor per Clause 7.3.2 confirms that every software-implemented risk control has a linked verification result demonstrating its effectiveness. Any risk control without verification evidence is treated as a critical gap blocking release of the Core Temperature Monitor Firmware.


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

[User]
Expand requirement SRS-FUNC-003: "audit trail and data export" (Category: functional)
Project: FallRisk Inpatient Assessment Tool | Fall Risk Assessment App | Class B
Calculating fall risk scores for hospitalized patients to guide nursing interventions. Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

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

[Assistant]
Description: All processed measurements shall be stored with timestamps in a persistent log accessible through web form for clinical review and regulatory audit.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

[User]
Write a SDP section on development platform and build infrastructure for FetalGuard Heart Rate Monitor, a Class B Fetal Heart Rate Monitor Firmware. Reference IEC 62304 Clause 5.1.4.
External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

[Assistant] Content: The FetalGuard Heart Rate Monitor build environment uses C (embedded) on ARM Cortex-M7. Continuous integration builds execute on every commit, ensuring early detection of compilation errors and regression failures. Toolchain versions are locked to the configuration baseline and recorded in the Software Configuration Management Plan.


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

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

[Assistant] Content: The HeartView Resting HR Display is developed in C (embedded) targeting the ARM Cortex-M0+ platform. Source code is maintained under version control with branching and tagging conventions defined in SOP-012. For the Class A Heart Rate Display Firmware, formal tool qualification is not required per IEC 62304; however, the development toolchain is verified to function correctly through routine build-and-test cycles.


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

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

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

[User]
Write a SAD section on architectural overview for Class B for InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: The InfuRate IV Flow Calculator architecture decomposes the Infusion Rate Calculator into software items aligned with functional domains: data acquisition from input sources, signal processing, and user interface rendering via desktop GUI. Inter-item interfaces are specified per Clause 5.3.2.


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

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clause 5.1.1.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: Development of the NutriView Food Diary is governed by this Software Development Plan, which addresses planning, requirements, implementation, and system verification per IEC 62304 Clause 5.1.1. The Class A safety classification means the Nutritional Tracking Display App poses no hazard potential; accordingly, the plan excludes unit testing, integration testing, and detailed design deliverables, keeping the process proportionate to the risk profile.


[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 RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clause 5.2.3.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: Software-implemented risk controls for the RadView DICOM Viewer 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 Medical Image Viewer.


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

"Problem resolution for the DermaScan AI follows Clause 9. Problem reports capture severity, affected version, and steps to reproduce (Clause 9.1). Investigation per Clause 9.2 determines root cause. Trends are analyzed per Clause 9.6 at each milestone review."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the DermaScan AI (skin lesion classifier, Class B). 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 NeuroStim Programmer (neurostimulator programmer, Class C):

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the NeuroStim Programmer (neurostimulator programmer, Class C). Standards references are accurate.


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 5.7, 5.7.1.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Verification of the InhaleSense Smart Inhaler Tracker consists exclusively of system-level testing per IEC 62304 Clause 5.7. Test cases derive from the software requirements specification and exercise the Smart Inhaler Adherence Tracker end-to-end on the nRF52832 (firmware) + iOS/Android (app) platform. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are not required for Class A software and are excluded from the verification scope.


[System] You are 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 RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 9.1, 9.2.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: The problem resolution process for the RadOnco Cloud Treatment Planner follows Clauses 9.1 through 9.8. Each problem report is classified by severity, investigated for root cause, and resolved through the change control process. Records are maintained per Clause 9.5, and all resolutions are verified per Clause 9.7 before the Cloud Radiation Treatment Planning SaMD baseline is updated.


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

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

"The VentAssist Pro addresses IEC 62304 Clause Annex A.1 for automated regression testing and Clause 5.8.9 for user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 5.8.9, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. Clause 5.8 has 5.8.1 through 5.8.8 only. All clause 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: "data integrity validation" (Category: data)
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: Data integrity of all stored records in the Cloud SaMD Histopathology Analysis Platform shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


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

[User]
Expand requirement SRS-SAFE-001: "fail-safe behavior specification" (Category: safety)
Project: ECGInsight Rhythm Interpreter | ECG Interpretation Service | Class B
Automated preliminary interpretation of 12-lead ECG recordings for physician review and overread. Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

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

[Assistant]
Description: The ECG Interpretation Service shall enter a defined safe state within the maximum allowable transition time when a critical fault is detected, ensuring no hazardous output persists.
Rationale: A deterministic safe-state transition prevents the ECG Interpretation Service from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: All 20 defined fault scenarios result in correct safe-state entry within timing limits across 10 iterations each.
Source: Risk control


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

"Software safety classification is performed per IEC 62304:2020 Clause 4.3."

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


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

[User]
Expand requirement SRS-FUNC-002: "audit trail and data export" (Category: functional)
Project: PaceSet Pacemaker Programmer | Cardiac Pacemaker Programmer Software | Class C
Programming and interrogating implanted cardiac pacemakers including rate settings, sensitivity, and output parameters. Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

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 Cardiac Pacemaker Programmer Software shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via proprietary RF.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Logged data is retrievable after power cycle, with all timestamps accurate to within 1 second of the reference clock.
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 InfuSafe Controller (insulin infusion pump controller, Class C):

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

[User]
Write a SDP section on configuration identification approach for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clauses 8.1, 8.1.1.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: Configuration items for the PathCloud AI Histology Analyzer include source code, build scripts, the SDP itself, software requirements, and verification records. Each item is uniquely identified by its path in the version control repository and its revision identifier, ensuring that any configuration baseline can be precisely reproduced as required by IEC 62304 Clause 8.1.


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

[User]
Expand requirement SRS-FUNC-004: "data acquisition from MAX30208 temperature sensor" (Category: functional)
Project: TempWatch Body Temperature Logger | Temperature Logging Firmware | Class A
Passive logging and display of skin temperature trends for personal interest. Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

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

[Assistant]
Description: The TempWatch Body Temperature Logger software shall acquire MAX30208 temperature sensor data at the specified sampling rate and store values in a circular buffer for processing by the Temperature Logging Firmware signal pipeline.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Temperature Logging Firmware.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


[System] You are 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 MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

[Assistant] Content: Traceability scope for the MedImage PACS Viewer 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 Web PACS Image Viewer.


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

[User]
Expand requirement SRS-PERF-003: "memory usage budget" (Category: performance)
Project: PulmoCheck Spirometry Analyzer | Spirometry Analysis Software | Class B
Analysis and interpretation of spirometry test data with predicted value comparison. Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

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

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


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

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

"The RetinaScan Pro 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 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 FetaSound (fetal heart rate monitor, Class B):

"REQ-SRS-056: Upon detecting a communication timeout with the sensor module, the FetaSound shall display a warning indicator within 1 second and log the event. Acceptance criterion: simulate timeout and verify warning display timing and log entry. Priority: Mandatory. Source: Risk control."

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


[System] You are an IEC 62304 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: SterilLog Sterilization Record System | Sterilization Record Logger | Class A
Recording and archiving sterilization cycle parameters for regulatory compliance. Software logging sterilization cycle parameters from autoclaves. Records temperature, pressure, and time for compliance documentation.

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

[Assistant]
Description: The SterilLog Sterilization Record System shall operate within the specified RAM and flash memory budget on the Windows desktop platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the Sterilization Record Logger, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


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

"ISO 13485-2 Section 5.1 requires all software units to be verified."

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


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

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


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

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

[Assistant] Content: Safety classification analysis per Clause 4.3 determined that the BalanceBoard Vestibular Trainer is Class B. The Balance Training Platform Firmware can contribute to a hazardous situation during Measuring postural sway and providing visual biofeedback during vestibular rehabilitation, but the hazard severity is limited to non-serious injury due to mitigating controls in the clinical environment. Architectural documentation and integration testing are mandated at this classification level.


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

[User]
Write a SDP section on development methodology for Class C with full V-model for NeoVent Neonatal Ventilator, a Class C Neonatal Ventilator Firmware. Reference IEC 62304 Clause 5.1.1.
Neonatal ventilator firmware supporting CPAP, NIPPV, and conventional ventilation for extremely premature infants. Tidal volumes as low as 2 mL.

[Assistant] Content: The NeoVent Neonatal Ventilator follows a strict V-model lifecycle with no phase abbreviations permitted. Requirements trace to architecture, architecture traces to detailed design, and each trace is verified by independent reviewers. Unit testing with coverage targets, integration testing, and system testing form the ascending verification arm, each gated by formal review of the Neonatal Ventilator Firmware test results.


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

[User]
Write a THREAT section on STRIDE threat categories applied to the device for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: The STRIDE analysis for the PainRelief PCA Pump Controller PCA Pump Controller Firmware evaluates six threat categories at each trust boundary: Spoofing (unauthorized entity impersonation), Tampering (data modification in transit or at rest), Repudiation (undetectable actions), Information Disclosure (data leakage), Denial of Service (availability disruption), and Elevation of Privilege (unauthorized capability access).


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

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

"The OxyPure Controller addresses IEC 62304 Clause 10.1 for security testing and Clause 6.4 for user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 10.1 and 6.4, neither of which exists. IEC 62304 has no Clause 10. Standard ends at Clause 9. Clause 6 has 6.1, 6.2, 6.3 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 Class A classification justification and implications for WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clause 4.3.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: Classification per Clause 4.3 places the WasteTrack Biohazard Logger in Safety Class A. The Biohazard Waste Tracking App cannot contribute to a hazardous situation -- all identified failure modes lead to degraded display or loss of informational features, not to patient harm. No external risk control is needed to justify this classification.


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

[User]
Expand requirement SRS-INTF-002: "clinical system integration interface" (Category: interface)
Project: BreathEasy Air Quality Display | Environmental Air Quality Display | Class A
Informational display of indoor air quality metrics for general awareness. Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

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

[Assistant]
Description: The BreathEasy Air Quality Display shall exchange data with external systems via I2C using the specified message format with error handling.
Rationale: Interoperability enables integration of Environmental Air Quality Display data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
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 risk control requirements traceability for InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clause 5.2.3.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: Software-implemented risk controls for the InfuRate IV Flow Calculator 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 Infusion Rate Calculator.


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

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

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

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


[System] You are 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 addresses IEC 62304 Clause 11.1 for security testing and Clause 9.9 for automated regression testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 11.1 and 9.9, neither of which exists. IEC 62304 has no Clause 11. Clause 9 has 9.1 through 9.8 only. 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 HeartLink (cardiac telemetry system, Class B):

"System testing for the HeartLink 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 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 AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: This plan applies to all software executing within the AirSentry Urban Air Quality Station Air Quality Monitoring Station Firmware and its supporting build and verification infrastructure. External systems that exchange data with the Air Quality Monitoring Station Firmware via 4G LTE are covered only at the interface boundary; their internal implementation is outside the scope of this SDP.


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

[Assistant] Content: The InfuRate IV Flow Calculator interfaces with external hardware via desktop GUI. Interface requirements specify the physical layer, data format, sampling rate, and error handling for each connection. All interface requirements are verifiable through integration or system testing.


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

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

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

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


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

[User]
Expand requirement SRS-DATA-002: "stored data corruption detection" (Category: data)
Project: AquaGuard Water Quality Monitor | Water Quality Monitoring Firmware | Class A
In-situ measurement of water quality parameters for environmental monitoring. Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

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 AquaGuard Water Quality Monitor shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

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

"The EchoAssist is designed to meet all applicable performance criteria. System requirements are addressed through appropriate design activities."

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


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

[User]
Expand requirement SRS-SEC-001: "user identity verification" (Category: security)
Project: AssetTrack Equipment Inventory | Equipment Inventory System | Class A
Tracking location and status of medical equipment for inventory management. Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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

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


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

[User]
Write a SRS section on operational context and user population for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 5.2.2.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The DoseLog Radiation Badge Reader operates as a Dosimetry Data Logger where Reading and archiving personal radiation exposure data from dosimeter badges. The software interfaces with dosimeter badge reader and communicates via USB, database. The operational environment, user population, and regulatory context described here constrain the requirements that follow.


[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 SterilLog Sterilization Record System, a Class A Sterilization Record Logger. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Software logging sterilization cycle parameters from autoclaves. Records temperature, pressure, and time for compliance documentation.

[Assistant] Content: The software system boundary for SterilLog Sterilization Record System encompasses the Sterilization Record Logger application and its direct interfaces: RS-232, database. Components outside this boundary -- including serial port data from autoclave 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 a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SRS section on functional requirements overview for 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: The RespiRate Respiratory Monitor functional requirements define what the Respiratory Rate Monitor Firmware does in response to user inputs, sensor data, and system events. Requirements are organized by functional area: data acquisition, signal processing, display and output, and system management. Each requirement is individually testable.


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

[Assistant] Content: The C++ (image processing) + Python (ML) + Swift/Kotlin (mobile alerts) compiler, test framework, and coverage analysis tools used for the StrokeAlert CT Perfusion Analyzer are qualified per Clause 5.1.4. Qualification includes comparison of tool output against known-correct reference results and documentation of tool version, configuration, and any known limitations affecting the AI Stroke Triage CT Perfusion SaMD 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 WoundTrack (wound measurement imaging system, Class B):

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


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

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

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

[Assistant]
Description: The InhaleSense Smart Inhaler Tracker shall operate within the specified RAM and flash memory budget on the nRF52832 (firmware) + iOS/Android (app) platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the Smart Inhaler Adherence Tracker, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


[System] You are a 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: "measurement data lifecycle" (Category: data)
Project: FetalGuard Heart Rate Monitor | Fetal Heart Rate Monitor Firmware | Class B
Continuous external fetal heart rate monitoring during labor with clinical display. External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

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

[Assistant]
Description: Measurement records stored by the Fetal Heart Rate Monitor Firmware shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Fetal Heart Rate Monitor Firmware.
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-PERF-002: "memory usage budget" (Category: performance)
Project: MindCalm Meditation Timer | Meditation Wellness App | Class A
Guided meditation timing with optional passive biometric display. Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

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

[Assistant]
Description: The MindCalm Meditation Timer memory footprint on iOS/Android shall remain within specified limits under worst-case operational scenarios.
Rationale: Exceeding memory limits could cause undefined behavior in the Meditation Wellness App, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

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

"Configuration management for the EchoAssist follows Clause 8. Configuration items are identified per Clause 8.1.1, SOUP is identified per Clause 8.1.2, and change control is managed per Clause 8.2. Status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the EchoAssist (echocardiogram analysis aid, 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 lightweight review process for Class A for DreamLog Sleep Monitor, a Class A Sleep Tracking Display App. Reference IEC 62304 Clause 5.1.1.
Companion app for a wearable sleep tracker. Displays sleep stages, duration, and trends. No alarms, no diagnostic claims.

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


[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 VentAssist Pro (ICU ventilator controller, Class C):

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

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


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

[User]
Write a SDP section on SOUP identification and management for ScreenFlow Population Health Screener, a Class A Serverless Population Health Screening SaMD. Reference IEC 62304 Clause 8.1.2.
Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

[Assistant] Content: SOUP components in the ScreenFlow Population Health Screener are catalogued per Clause 8.1.2 with title, version, supplier, and license terms. The risk management process evaluates each SOUP item's known anomaly list per Clause 7.1.3 to determine whether any published defect could contribute to a hazardous situation in the Serverless Population Health Screening 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 purpose and scope for Class B with moderate documentation for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.1.1.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: This plan establishes the development framework for the TriagePro Emergency Scoring App Emergency Department Triage SaMD, 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 TRACE section on risk control coverage verification for HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

[Assistant] Content: The HandGrip Strength Dynamometer gap analysis per Clause 5.7.4 and Clause 7.3.2 verifies that the risk control traceability chain is complete. Every hazard in the risk management file that has a software control must trace to a verified requirement in the Hand Dynamometer Firmware. Incomplete chains are flagged and resolved before release.


[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-002: "display update rate for Cloud ECG Analysis SaMD" (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: Output presentation on the REST API shall refresh at the configured interval, reflecting the most recent processed data from the Cloud ECG Analysis SaMD pipeline.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
Source: User need


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

[User]
Expand requirement SRS-INTF-002: "conductivity sensors (x2) communication specification" (Category: interface)
Project: DialyFlow Dialysis Fluid Controller | Hemodialysis Fluid Controller Firmware | Class C
Controlling dialysate composition, flow rates, and ultrafiltration in hemodialysis. Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

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

[Assistant]
Description: The Hemodialysis Fluid Controller Firmware sensor interface shall establish and maintain reliable communication with the conductivity sensors (x2) via CAN bus.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Hemodialysis Fluid Controller Firmware output.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

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

[Assistant] Content: Security requirements for the WaveReview EEG Archive Viewer address authentication, data protection, and access control for the EEG Archive Viewer. All persistent data is encrypted at rest, and data in transit over desktop GUI uses transport layer encryption. Security requirements are aligned with IEC 81001-5-1:2021.


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

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

[Assistant] Content: Coverage analysis for the GrowthChart Pediatric Viewer per Clause 5.7.4 confirms that every SRS requirement maps to at least one test case with a passing result. Requirements implementing risk controls are additionally confirmed to have adequate test coverage. The Growth Chart Display App release is contingent on 100% requirement coverage with no open gaps.


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

[User]
Write a SDP section on Class A classification justification and implications for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clause 4.3.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: Under IEC 62304 Clause 4.3, the NutriView Food Diary is classified as Safety Class A. The Nutritional Tracking Display App is a purely informational system for Personal food logging and nutritional data visualization with no control over therapeutic delivery, diagnostic decision-making, or life-sustaining functions. Software failure would result in loss of informational display, not patient harm.


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

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

"Maintenance activities follow ISO 14971:2020 Clause 6."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971:2020" which is incorrect. No 2020 edition. Current: ISO 14971:2019. All references must be corrected.


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

"Unit verification per IEC 62304 Clause 5.5 requires testing of all StepTrack software units."

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


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

[User]
Write a SRS section on resource constraints and scalability for PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clause 5.2.2.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Resource requirements for the PharmaSafe CDSS specify maximum memory utilization, persistent storage consumption, and processor loading on Kubernetes (on-premise hospital data center). The Clinical Decision Support System must operate within these constraints under worst-case conditions without degradation of safety-relevant functions.