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

[User]
Expand requirement SRS-DATA-002: "data retention period" (Category: data)
Project: 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: Data retention in the DialyFlow Dialysis Fluid Controller shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Hemodialysis Fluid Controller Firmware.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


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

[User]
Write a SDP section on change control and trend analysis for problems for ChemoFlow Infusion Controller, a Class C Chemotherapy Infusion Pump Firmware. Reference IEC 62304 Clauses 9.4, 9.6.
Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

[Assistant] Content: Corrections to the ChemoFlow Infusion Controller follow the change control process per Clause 9.4, with regression testing proportional to the scope of the change. Problem reports are periodically analyzed for trends per Clause 9.6 to identify systemic issues in the development process that might affect the quality of the Chemotherapy Infusion Pump 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-SEC-002: "access control and authorization" (Category: security)
Project: ChemoFlow Infusion Controller | Chemotherapy Infusion Pump Firmware | Class C
Precision-controlled chemotherapy drug infusion with dose-error detection and safety interlocks. Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

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

[Assistant]
Description: Access to configuration and administrative functions of the Chemotherapy Infusion Pump Firmware shall be restricted to authenticated and authorized users.
Rationale: Unauthorized configuration changes to the Chemotherapy Infusion Pump Firmware could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

[User]
Expand requirement SRS-FUNC-005: "device configuration management" (Category: functional)
Project: SurgLog Procedure Documentation App | Surgical Documentation App | Class A
Documentation and review of surgical procedure notes. Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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 Surgical Documentation App shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Parameter flexibility is essential for the Surgical Documentation App to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User]
Write a SDP section on milestones and phase transition criteria for CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clause 5.1.1.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

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


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

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

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

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


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-003: "user-configurable operating parameters" (Category: functional)
Project: StrokeAlert CT Perfusion Analyzer | AI Stroke Triage CT Perfusion SaMD | Class C
Rapid automated CT perfusion analysis generating ischemic core and penumbra maps for acute stroke treatment decisions. 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.

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

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


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

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

"Configuration management follows industry best practices. All items are controlled as appropriate for the FetaSound development effort."

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


[System] You are a 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: "external system data exchange" (Category: interface)
Project: RemotICU Continuous Monitoring Hub | Edge-to-Cloud ICU Monitoring Gateway | Class B
Aggregating bedside monitor data at the edge and streaming to cloud for tele-ICU clinical oversight. Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

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

[Assistant]
Description: Data interoperability with clinical information systems shall be provided through HL7v2 ADT/ORU, supporting standard message formats.
Rationale: Interoperability enables integration of Edge-to-Cloud ICU Monitoring Gateway data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

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

[Assistant] Content: The RetinaStim Visual Prosthesis Controller cybersecurity posture is defined per IEC 81001-5-1:2021, covering threat modeling, secure design, vulnerability management, and incident response for the Retinal Prosthesis Controller Firmware. Health software product safety requirements from IEC 82304-1:2016 supplement the IEC 62304 lifecycle where applicable.


[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: "continuous data sampling from primary sensor" (Category: functional)
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 from the primary sensor shall be acquired by the PathCloud AI Histology Analyzer at the configured rate, with each sample timestamped and queued for processing.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for AI-assisted identification of suspicious regions in digitized histology slides for pathologist review.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a TRACE section on traceability scope including risk controls for CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

[Assistant] Content: The CleanRoom Particle Counter Logger matrix traces two categories per Clause 5.7.1 and Clause 7.3.2: functional requirements (from system specification through design to test) and risk control requirements (from hazard analysis through SRS to verification). Both categories must show complete coverage before release of the Cleanroom Environmental Logger.


[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 A for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 5.1.1.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: An iterative development approach with defined phase gates is adopted for the SunGuard UV Index Display, appropriate for the Class A classification where system-level verification is the primary quality gate. Each iteration produces a testable increment of the UV Exposure Display Firmware functionality, with reviews at Requirements Complete, Implementation Complete, and Release Readiness milestones.


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

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

"The ThermoGuard development follows IEC 62304-1 for the software lifecycle."

[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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on acceptance criteria and independent review for Class C for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clauses 5.5.3, 5.5.5, 5.7.4.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: For the NeoFeed Neonatal Feeding Pump, unit acceptance criteria per Clause 5.5.3 include correct functionality, absence of critical anomalies, and coverage metrics at or above the defined thresholds. Additional unit acceptance criteria per Clause 5.5.4 address coding standards compliance and absence of dead code. Independent review confirms all criteria are met before integration of the Neonatal Feeding Pump Firmware components.


[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: "data processing timing constraint" (Category: performance)
Project: PedDose Pediatric Dosing App | Pediatric Dosing Calculator App | Class B
Weight-based pediatric dose calculations with age-appropriate range checking. Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

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

[Assistant]
Description: End-to-end latency from primary sensor data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Real-time performance is critical for the Pediatric Dosing Calculator App to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


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

[User]
Write a SDP section on internal SOPs and procedures for WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clause 5.1.2.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

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


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

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

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

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


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

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

[Assistant] Content: Risk control verification for the SurgLog Procedure Documentation App per Clause 7.3.1 is performed as part of the applicable testing levels. Each risk control measure is traced per Clause 7.3.2 from the ISO 14971 risk analysis through the SRS to the test result confirming its implementation in the Surgical Documentation App.


[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 ThermoGuard (body temperature logger, Class A):

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

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


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

[User]
Write a TRACE section on traceability scope including risk controls for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

[Assistant] Content: The ClinTrial EDC Platform traceability matrix extends beyond functional requirements to include risk control traceability per Clause 7.3.2. Each risk control measure implemented in the Clinical Trial EDC Web Platform software is traced from the ISO 14971 hazard through the software requirement to the verification test confirming its effectiveness.


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

[User]
Write a SRS section on data retention and integrity requirements for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clause 5.2.2.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

[Assistant] Content: Persistent data managed by the VitalPulse SpO2 Monitor includes configuration parameters, acquired measurements from MAX30102 dual-wavelength PPG, and operational logs. Data integrity requirements specify error detection mechanisms and the Pulse Oximeter Firmware response to data corruption events.


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

[User]
Expand requirement SRS-FUNC-004: "audit trail and data export" (Category: functional)
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 maintain a timestamped record of all measurements in non-volatile storage, supporting export via DICOM ECG input.
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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"The PillRemind 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 PillRemind medication reminder app. 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 CardioPulse Monitor (cardiac rhythm monitor, Class B):

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

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


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

[User]
Expand requirement SRS-FUNC-006: "configurable alarm limits for monitored parameters" (Category: functional)
Project: RenalDose Renal Adjustment Calculator | Renal Dose Adjustment Calculator | Class B
Calculating renal-adjusted medication doses based on estimated glomerular filtration rate. Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

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

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


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

[User]
Write a SDP section on verification strategy for Class B -- integration and system testing for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clauses 5.6, 5.6.3, 5.7.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: The PathCloud AI Histology Analyzer verification plan includes two mandatory levels: integration testing per Clause 5.6 and system testing per Clause 5.7. Unit testing is recommended for safety-relevant modules identified in the risk analysis but is not a mandatory deliverable at Class B. Integration tests confirm that software items interact correctly in the Cloud SaMD Histopathology Analysis Platform architecture.


[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 software development conforms to ISO 13485-1, with risk management per ISO 14971:2019."

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


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

[User]
Write a SDP section on problem reporting and investigation for VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clauses 9.1, 9.2.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

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


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

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

[Assistant] Content: Data processing requirements for the BeamPlan Radiation Treatment Planner define the transformations applied to raw input from data sources to produce the output presented to the user. Each transformation has defined accuracy bounds and error handling behavior specific to the Radiation Treatment Planning Software operational context.


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

[User]
Write a SDP section on tool qualification for Class B and C for HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clause 5.1.4.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

[Assistant] Content: Tools used in verification of the HandGrip Strength Dynamometer undergo qualification per IEC 62304 Clause 5.1.4. This includes the C (embedded) compiler, static analysis tools, and test execution frameworks. Qualification evidence demonstrates that each tool produces correct and repeatable results for the verification activities it supports.


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

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

[Assistant] Content: The TriagePro Emergency Scoring App risk control verification per Clause 7.3.1 exercises each control measure in isolation and in the context of the complete Emergency Department Triage SaMD. Clause 7.3.3 documentation records the verification method, the test result, and the conclusion regarding the control's effectiveness.


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

[User]
Write a SRS section on sensor and communication protocol requirements for FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: Interface requirements for the FactoryTemp Industrial Temperature Monitor specify the communication protocols, data formats, and timing constraints for each external interface of the Industrial Temperature Monitoring Firmware. The primary data acquisition interface uses Modbus RTU with specified data rates and error detection mechanisms.


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

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

"ISO 62304 Section 5.7 requires all software units to be verified."

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


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

[User]
Write a SRS section on external system communication requirements for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clause 5.2.2.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

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


[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 VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clause 5.2.2.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

[Assistant] Content: This section describes the operational context of the VibeCheck Vibration Analyzer Vibration Analysis Instrument Firmware. The system is intended for Vibration spectrum analysis of industrial machinery for predictive maintenance, operating on ARM Cortex-A7 with DSP. Key interfaces include BNC input, USB, LCD. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

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

"Cybersecurity considerations are addressed as applicable to the chemotherapy dose calculator. Controls are implemented following industry best practices and guidance."

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


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

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

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


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

[User]
Expand requirement SRS-SAFE-001: "safety classification confirmation for Class A" (Category: safety)
Project: FactoryTemp Industrial Temperature Monitor | Industrial Temperature Monitoring Firmware | Class A
Continuous monitoring and logging of factory floor temperatures for process control. Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

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

[Assistant]
Description: The Industrial Temperature Monitoring Firmware software functions are limited to informational display and data presentation, with no capability to influence clinical decisions or therapeutic actions.
Rationale: The Class A classification of the Industrial Temperature Monitoring Firmware depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Code review confirms no software path exists that controls therapeutic outputs, modifies diagnostic results, or generates clinical alerts.
Source: Regulatory


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

[User]
Review this documentation excerpt for the NurseCall Hub (patient call system dashboard, Class A):

"The NurseCall Hub verification strategy addresses only system testing as mandated for Class A software per IEC 62304. Each software requirement has at least one corresponding system test case. No unit or integration testing is specified because Class A software cannot contribute to a hazardous situation."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification; 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 Class A classification justification and implications for HydroRemind Hydration Tracker, a Class A Hydration Tracking Firmware. Reference IEC 62304 Clause 4.3.
Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

[Assistant] Content: Classification per Clause 4.3 places the HydroRemind Hydration Tracker in Safety Class A. The Hydration Tracking Firmware 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 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 CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: The CogniTest Cognitive Assessment App SOUP risk assessment per Clause 7.1.3 documents all known SOUP defects relevant to the Cognitive Assessment Application operational context. Where a SOUP defect could contribute to a hazardous situation, the architecture implements a software-level mitigation or the affected SOUP component is replaced.


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

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

"Risk management for the CaloriePal follows Clause 7. Software items contributing to hazardous situations are identified per Clause 7.1.1. Risk control measures are defined per Clause 7.2.1 and verified per Clause 7.3.1. Traceability is documented per Clause 7.3.2."

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


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

[User]
Write a SDP section on cybersecurity and health IT standards for MindCalm Meditation Timer, a Class A Meditation Wellness App. Reference IEC 62304 Clause 5.1.2.
Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

[Assistant] Content: The MindCalm Meditation Timer cybersecurity posture is defined per IEC 81001-5-1:2021, covering threat modeling, secure design, vulnerability management, and incident response for the Meditation Wellness App. Health software product safety requirements from IEC 82304-1:2016 supplement the IEC 62304 lifecycle where applicable.


[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 integration test plan addresses Clause 5.6.1 through 5.6.7. Software units are integrated incrementally with testing at each step. Test content per Clause 5.6.4 covers data integrity, timing constraints, and fault tolerance. Test records meet Clause 5.6.7 requirements."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the ChemoCalc (chemotherapy dose calculator, Class C). Standards references are accurate.


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-2" which is incorrect. IEC 62304 has no Part 2. It is a single-part standard. All references must be corrected.


[System] You are 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 RadView DICOM (DICOM image viewer, Class A):

"The RadView DICOM integration test suite validates all APIs, shared memory interfaces, and IPC mechanisms between software items."

[Assistant]
Verdict: FAIL
Note: Content mandates integration testing of all interfaces 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 primary international standards applicable to development for PulmoCheck Spirometry Analyzer, a Class B Spirometry Analysis Software. Reference IEC 62304 Clause 5.1.2.
Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

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


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

[Assistant] Content: Data within the PathCloud AI Histology Analyzer Cloud SaMD Histopathology Analysis Platform traverses three processing stages: acquisition, analysis, and presentation. Each stage is implemented as an independent software item with typed interfaces per Clause 5.3.2. The architecture ensures data integrity is verifiable at each stage boundary during integration testing.


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

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

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

[Assistant]
Description: The InhaleSense Smart Inhaler Tracker startup sequence shall include diagnostic checks of all critical subsystems and report any detected faults before allowing operational use.
Rationale: Startup verification prevents the Smart Inhaler Adherence Tracker from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

[User]
Write a SRS section on baseline security requirements for PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clause 5.2.2.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: Baseline security requirements for the PathSlide Digital Pathology Viewer ensure the Digital Pathology Viewer protects user data, resists unauthorized access, and maintains audit trails. Data communicated via WebSocket tile streaming is encrypted. Access is controlled through authentication mechanisms appropriate to the deployment environment.


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

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

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

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


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

[User]
Write a SDP section on verification strategy for Class B -- integration and system testing for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clauses 5.6, 5.6.3, 5.7.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: Integration and system testing constitute the mandatory verification activities for the HemaCount Digital Cell Counter IVD Digital Cell Counter Software at Class B. Integration tests per Clause 5.6 verify data exchange across architectural boundaries, while system tests per Clause 5.7 exercise the complete software against the SRS. Unit testing may be applied to selected modules but is not required.


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

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

[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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on purpose of the SRS document for WaterPure Quality Logger, a Class A Water Quality Data Logger. Reference IEC 62304 Clause 5.2.1.
Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

[Assistant] Content: This document specifies the software requirements for the WaterPure Quality Logger Water Quality Data Logger as required by IEC 62304 Clause 5.2.1. It serves as the primary input to design and the primary reference for verification test case derivation. All requirements are verifiable, traceable, and configuration-controlled.


[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 purpose and scope of the traceability matrix for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clause 5.7.1.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: The purpose of this traceability matrix is to confirm complete coverage of the NeoFeed Neonatal Feeding Pump software requirements through design and verification per Clause 5.7.1. Bidirectional tracing enables identification of gaps (unimplemented requirements) and orphans (implementations without requirements) in the Neonatal Feeding Pump Firmware.


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

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

"Per IEC 62304 Clause 5.7, system testing is performed. Per IEC 62304 Clause 5.7, the system is tested. Per IEC 62304 Clause 5.7, system-level verification is conducted. Per IEC 62304 Clause 5.7, the NeuroStim Programmer undergoes system testing."

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


[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 scope boundaries of the software system for CardioRhythm ECG Analyzer, a Class B Single-Lead ECG Device Firmware. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay diagnosis.

[Assistant] Content: This plan applies to all software executing within the CardioRhythm ECG Analyzer Single-Lead ECG Device Firmware and its supporting build and verification infrastructure. External systems that exchange data with the Single-Lead ECG Device Firmware via SPI 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 SDP section on hazard identification for the specific device for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: For the DoseCalc Medication Calculator, potential software contributions to hazardous situations include input data corruption, processing algorithm errors, and manual data entry communication failures. Each identified cause is evaluated for severity and probability, with risk control measures defined per Clause 7.2.1 and traced to software requirements.


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clauses 5.7, 5.7.1.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: The VisitorPass Access Management verification strategy relies solely on system testing, consistent with Class A requirements under IEC 62304. Each software requirement maps to at least one system test case, validated against the Visitor Management System in its operational environment. No unit testing or integration testing is performed -- these activities are not mandated for Class A and would add unnecessary process overhead for the Visitor Management System.


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

[User]
Expand requirement SRS-DATA-001: "measurement data lifecycle" (Category: data)
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: Measurement records stored by the Artificial Pancreas Controller Firmware shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

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

[Assistant] Content: The GaitSense Walking Analysis SRS follows a structured format: each requirement has a unique ID, a type classification, a priority, a rationale, and acceptance criteria per Clause 5.2.2. Requirements implementing risk control measures per Clause 5.2.3 are explicitly marked to ensure they receive verification attention proportional to their safety significance.


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

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

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

[Assistant]
Description: The Claims Processing Service shall support bidirectional data exchange with external systems over X12 EDI.
Rationale: Interoperability enables integration of Claims Processing Service data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

"Each StepTrack software unit has a detailed design specification reviewed before implementation."

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


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

[User]
Write a SDP section on change control and trend analysis for problems for CardioRhythm ECG Analyzer, a Class B Single-Lead ECG Device Firmware. Reference IEC 62304 Clauses 9.4, 9.6.
Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay diagnosis.

[Assistant] Content: All CardioRhythm ECG Analyzer problem corrections enter the change control process per Clause 9.4 before integration into the baseline. Trend analysis per Clause 9.6 tracks defect density, time-to-resolution, and defect category distribution across the Single-Lead ECG Device Firmware development lifecycle to drive process improvement.


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

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

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

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


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

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

"Maintenance activities follow IEC 62304:2015 Clause 6."

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


[System] You are a 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: "data retention period" (Category: data)
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 shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Meditation Wellness App.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Write a SDP section on change control and trend analysis for problems for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clauses 9.4, 9.6.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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


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

[User]
Expand requirement SRS-PERF-002: "computational accuracy requirement" (Category: performance)
Project: RetinaScan Diabetic Retinopathy Screener | Retinal Screening Software | Class B
AI-assisted screening of retinal images for diabetic retinopathy signs, requiring specialist confirmation. Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist 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: Output accuracy of the Retinal Screening Software shall meet or exceed the specified tolerance for all measurement parameters across operating conditions.
Rationale: Inaccurate output from the Retinal Screening Software 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 a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

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

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


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

[User]
Write a SRS section on baseline security requirements for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clause 5.2.2.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: Security requirements for the ThermoWatch Core Temperature Monitor address authentication, data protection, and access control for the Core Temperature Monitor Firmware. All persistent data is encrypted at rest, and data in transit over LCD uses transport layer encryption. Security requirements are aligned with IEC 81001-5-1:2021.


[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-002: "Class A scope validation" (Category: safety)
Project: FactoryTemp Industrial Temperature Monitor | Industrial Temperature Monitoring Firmware | Class A
Continuous monitoring and logging of factory floor temperatures for process control. Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

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

[Assistant]
Description: The Industrial Temperature Monitoring Firmware software functions are limited to informational display and data presentation, with no capability to influence clinical decisions or therapeutic actions.
Rationale: Confirming the absence of safety-relevant functions validates the Class A classification under IEC 62304 Clause 4.3.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Industrial Temperature Monitoring Firmware.
Source: Regulatory


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

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

"Software development follows IEC 62304 Clause 5.9 requirements for security testing."

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


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

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

"Compliance with IEC 62304 Clause 5.1.12 is demonstrated through detailed design verification."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.1.12 which does not exist. Clause 5.1 has 5.1.1 through 5.1.11 only. The reference must be corrected to a valid clause number.


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

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

[Assistant] Content: The LabView Results Portal review process is proportionate to the Class A risk level. The project lead reviews each deliverable for technical accuracy, and the quality representative verifies compliance with SOPs. Reviews are documented but do not require independent technical review of the Laboratory Results Viewer verification activities.


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

[Assistant] Content: The DoseVerify In-Vivo Dosimetry System traceability matrix provides end-to-end requirement coverage evidence per Clause 5.7.1. Every SRS requirement for the In-Vivo Dosimetry Verification Software is traced to its implementing software item and to the verification test case(s) confirming correct implementation. Orphaned requirements and untested implementations are flagged for resolution.


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

[User]
Write a SDP section on internal SOPs and procedures for FallRisk Inpatient Assessment Tool, a Class B Fall Risk Assessment App. Reference IEC 62304 Clause 5.1.2.
Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

[Assistant] Content: Work instructions for the FallRisk Inpatient Assessment Tool are codified in SOPs maintained within the ISO 13485 quality management system. SOP-010 (development planning), SOP-011 (risk management), SOP-012 (configuration management), and SOP-013 (verification) define step-by-step procedures for each IEC 62304 lifecycle activity applicable to the Fall Risk Assessment App.


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

[User]
Write a SDP section on Class B classification justification and implications for FallRisk Inpatient Assessment Tool, a Class B Fall Risk Assessment App. Reference IEC 62304 Clause 4.3.
Web app calculating fall risk scores for inpatients based on mobility, medication, and cognitive assessments.

[Assistant] Content: Under IEC 62304 Clause 4.3, the FallRisk Inpatient Assessment Tool is classified as Safety Class B. The Fall Risk Assessment App can contribute to a hazardous situation through Calculating fall risk scores for hospitalized patients to guide nursing interventions, but the identified hazards are mitigated by clinical workflow safeguards that prevent progression to serious injury or death. This classification drives the requirement for architectural design documentation and integration testing.


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

[User]
Write a SDP section on cybersecurity and health IT standards for HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clause 5.1.2.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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


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

[User]
Expand requirement SRS-INTF-001: "primary sensor interface protocol" (Category: interface)
Project: HeartView Resting HR Display | Heart Rate Display Firmware | Class A
Passive display of resting heart rate for wellness monitoring. Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical 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 Heart Rate Display Firmware sensor interface shall establish and maintain reliable communication with the MAX30102 PPG sensor via I2C.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Heart Rate Display Firmware output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Write a FMEA section on documenting failure modes and their effects for SupplyChain Procurement Portal, a Class A Supply Chain Procurement System. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

[Assistant] Content: The SupplyChain Procurement Portal 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 Supply Chain Procurement System output, and the resulting hazard severity. This documentation is maintained in the risk management file.


[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 RetinaScan Pro (diabetic retinopathy screening AI, Class B):

"ISO 62304 Section 5.5 requires all software units to be verified."

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


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

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

"The MedInventory verification strategy mandates unit testing with 90% statement coverage, integration testing of all component interfaces, and system-level testing."

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


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

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the RadView DICOM (DICOM image viewer, Class A). Standards references are accurate.


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

[User]
Write a SRS section on purpose of the SRS document for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clause 5.2.1.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: The purpose of this SRS is to establish the complete set of software requirements for the AutoclaveLog Cycle Recorder, providing the basis for design, implementation, and verification of the Sterilization Cycle Data Logger. Requirements are organized by type and traced to their originating system requirement, risk control measure, or stakeholder need per Clause 5.2.1.


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

[User]
Write a SDP section on change control process for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clauses 8.2, 8.2.1.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: No change to the VisitorPass Access Management 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 milestones and phase transition criteria for HydroRemind Hydration Tracker, a Class A Hydration Tracking Firmware. Reference IEC 62304 Clause 5.1.1.
Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

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


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

[User]
Write a FMEA section on failure mode identification approach for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

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


[System] You are a 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: "resource utilization limits" (Category: performance)
Project: StrokeAlert CT Perfusion Analyzer | AI Stroke Triage CT Perfusion SaMD | Class C
Rapid automated CT perfusion analysis generating ischemic core and penumbra maps for acute stroke treatment decisions. 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.

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 StrokeAlert CT Perfusion Analyzer shall operate within the specified RAM and flash memory budget on the AWS dedicated GPU + CloudFront + iOS/Android native app platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the AI Stroke Triage CT Perfusion SaMD, 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-003: "data acquisition from primary sensor" (Category: functional)
Project: VitalBoard Patient Summary | Patient Summary Dashboard | Class A
Read-only display of patient vital sign history for clinical reference. Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend 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: Data from the primary sensor shall be acquired by the VitalBoard Patient Summary at the configured rate, with each sample timestamped and queued for processing.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Patient Summary Dashboard.
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