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

[User]
Expand requirement SRS-INTF-003: "sensor data link requirements" (Category: interface)
Project: LabView Results Portal | Laboratory Results Viewer | Class A
Read-only display of laboratory test results for clinician reference. Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

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

[Assistant]
Description: The Laboratory Results Viewer sensor interface shall establish and maintain reliable communication with the primary sensor via HL7 FHIR API.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Laboratory Results Viewer output.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


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

[User]
Write a SDP section on scope boundaries of the software system for CardioLoop Cardiac Resync Controller, a Class C CRT Optimization Firmware. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Firmware for cardiac resynchronization therapy devices optimizing biventricular pacing based on hemodynamic feedback.

[Assistant] Content: This plan applies to all software executing within the CardioLoop Cardiac Resync Controller CRT Optimization Firmware and its supporting build and verification infrastructure. External systems that exchange data with the CRT Optimization Firmware via RF telemetry 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-005: "data logging and retrieval" (Category: functional)
Project: CogniTest Cognitive Assessment App | Cognitive Assessment Application | Class B
Administering and scoring standardized cognitive screening tests for clinical neuropsychological assessment. Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

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

[Assistant]
Description: The CogniTest Cognitive Assessment App shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via local database.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

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

"The PhysioTrack Rehab addresses IEC 62304 Clause 5.3.7 for automated regression testing and Clause 7.5 for performance benchmarking."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.3.7 and 7.5, neither of which exists. Clause 5.3 has 5.3.1 through 5.3.6 only. Clause 7 ends at 7.4. All clause references must be corrected.


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

[User]
Write a FMEA section on failure mode identification approach for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: The failure mode identification for the VisitorPass Access Management Visitor Management System 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-FUNC-005: "startup diagnostic verification" (Category: functional)
Project: PowerTrack UPS Monitor | UPS Monitoring Software | Class A
Logging and displaying UPS status for facility infrastructure monitoring. Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

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

[Assistant]
Description: Upon power-up, the PowerTrack UPS Monitor shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: A power-on self-test confirms hardware and software readiness before the UPS Monitoring Software begins use.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[User]
Write a SRS section on purpose of the SRS document for DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 5.2.1.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The SRS for the DoseLog Radiation Badge Reader documents every functional, performance, interface, and safety requirement governing the Dosimetry Data Logger. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


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

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

"The DermaScan AI addresses IEC 62304 Clause Annex A.1 (automated regression testing) through formal review."

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


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

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

"All verification for the wellness pedometer app follows IEC 62304-4 requirements."

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


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

[User]
Expand requirement SRS-SAFE-001: "fail-safe behavior specification" (Category: safety)
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: Upon detection of a critical software fault, the RenalDose Renal Adjustment Calculator shall transition to its defined safe state within the specified time, disabling any active output that could contribute to harm.
Rationale: A deterministic safe-state transition prevents the Renal Dose Adjustment Calculator from operating in an unknown or hazardous state after a detected fault.
Priority: Mandatory
Acceptance Criterion: Safe state transition completes within the specified time limit for each defined critical fault, verified by fault injection during operation.
Source: Risk control


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

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

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

[Assistant] Content: Traceability scope for the InfuRate IV Flow Calculator includes both functional requirements and risk control measures. Risk control traceability per Clause 7.3.2 links each hazard cause to the software control, the SRS requirement, the implementation, and the verification evidence for the Infusion Rate Calculator.


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

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

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

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


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

[Assistant] Content: Information security for the AirSentry Urban Air Quality Station Air Quality Monitoring Station 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 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):

"Referenced standards for the PillRemind include IEC 62304:2006+AMD1:2015 (software lifecycle), ISO 14971:2019 (risk management), and ISO 13485:2016 (QMS). IEC 81001-5-1:2021 is referenced for cybersecurity considerations."

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


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

[User]
Write a SAD section on SOUP component integration and requirements for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: SOUP components in the NutriView Food Diary are integrated through defined interfaces per Clause 5.3.3. For each component, the architecture specifies the functions used, the performance expectations, and the iOS/Android requirements per Clause 5.3.4. SOUP anomaly evaluation per Clause 7.1.3 is documented in the risk management file.


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clauses 5.7, 5.7.1.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

[Assistant] Content: The VibeCheck Vibration Analyzer 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 Vibration Analysis Instrument Firmware 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 Vibration Analysis Instrument 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 RadBeam Planner (radiation therapy planning system, Class C):

"Verification activities follow IEC 62304 Clause 5.1.12 for automated regression testing."

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

[User]
Expand requirement SRS-PERF-002: "end-to-end processing latency" (Category: performance)
Project: IncidentReport Clinical Event Logger | Incident Reporting System | Class A
Submission and routing of clinical incident reports for quality review. Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

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

[Assistant]
Description: End-to-end latency from primary sensor data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Bounded processing latency ensures the Incident Reporting System provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


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

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

"The CardioPulse Monitor follows the software lifecycle. The CardioPulse Monitor implements the lifecycle processes. The CardioPulse Monitor adheres to the lifecycle model. The CardioPulse Monitor conforms to the lifecycle framework."

[Assistant]
Verdict: FAIL
Note: The documentation section exhibits repeated project name. The project name 'CardioPulse Monitor' appears excessively. Sentences repeat the same assertion about the cardiac rhythm monitor in different words. Content should be consolidated and each sentence should contribute unique, specific information about the CardioPulse Monitor.


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

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

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

[Assistant]
Description: Upon power-up, the ConsentView Informed Consent Archive shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Consent Document Viewer 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 compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"Applicable standards for the HydroLog are: IEC 62304:2006+AMD1:2015 for the software development lifecycle, ISO 14971:2019 for risk management, and ISO 13485:2016 for the quality management system. No sub-part standards are referenced as IEC 62304 and ISO 14971 are each single-part standards."

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


[System] You are a regulatory 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 operational context and user population for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clause 5.2.2.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: The NeuroTune DBS Programmer operates as a Deep Brain Stimulator Programmer App where Programming stimulation parameters of implanted deep brain stimulators for Parkinson's disease management. The software interfaces with NFC/BLE telemetry and communicates via BLE 5.0, tablet GUI. The operational environment, user population, and regulatory context described here constrain the requirements that follow.


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

[User]
Expand requirement SRS-PERF-003: "computational accuracy requirement" (Category: performance)
Project: CogniTest Cognitive Assessment App | Cognitive Assessment Application | Class B
Administering and scoring standardized cognitive screening tests for clinical neuropsychological assessment. Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

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

[Assistant]
Description: Computational results produced by the CogniTest Cognitive Assessment App shall be accurate to within the specified tolerance, validated against reference calculations.
Rationale: Measurement accuracy directly affects clinical decisions based on the Cognitive Assessment Application output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Statistical analysis of 500 measurements shows mean error within tolerance and standard deviation within specified limits.
Source: Regulatory


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

[User] Is ISO 14971-1 a valid standard?

[Assistant] No. ISO 14971 is a single-part standard. There is no ISO 14971-1. The correct citation is ISO 14971:2019. For guidance on applying ISO 14971, refer to ISO/TR 24971:2020, which is a separate technical report.


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

[User]
Write a SRS section on data processing and transformation requirements for 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: Processing requirements for the VitalPulse SpO2 Monitor Pulse Oximeter Firmware cover data acquisition, filtering, computation, and presentation. Each processing step has specified input ranges, output tolerances, and error conditions. Data integrity is maintained throughout the processing pipeline.


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

[User]
Expand requirement SRS-FUNC-001: "data acquisition from tablet microphone" (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: The SurgLog Procedure Documentation App shall continuously sample tablet microphone data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Surgical Documentation App.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

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

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

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

[Assistant] Content: A modified V-model lifecycle is adopted for the DermaAssist Skin Lesion Classifier, incorporating iterative refinement within each phase while maintaining the formal verification traceability required at Class B. The Skin Lesion Classification App architecture must be verified before implementation begins, and integration testing must confirm interface correctness before system testing.


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

[User]
Write a SDP section on primary international standards applicable to development for TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clause 5.1.2.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

[Assistant] Content: Applicable standards for the TeleRehab Remote Patient Monitor 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 Remote Rehabilitation Platform.


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

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.2.3.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

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


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

[User]
Write a THREAT section on threat model data flow decomposition for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clause 5.2.2.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: Threat model decomposition for the NeuroTune DBS Programmer uses data flow diagrams at two levels of detail: a context diagram showing the Deep Brain Stimulator Programmer App and all external entities, and a level-1 diagram showing internal processes and data stores. Each data flow crossing a trust boundary is subject to STRIDE analysis.


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

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

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

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


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

[User]
Write a SDP section on scope boundaries of the software system for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: Scope is limited to the AllergyCard Patient Allergy Viewer software items developed under this plan and released as a single configuration baseline. Peripherals, test jigs, and cloud infrastructure used during Read-only display of patient allergy information at point of care are addressed by separate system-level documentation and are not governed by IEC 62304 Clause 5.1.1 activities described herein.


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

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

"The CardioPulse Monitor architecture is defined. The CardioPulse Monitor architecture is documented. The CardioPulse Monitor architecture is verified. The CardioPulse Monitor architecture is reviewed. The CardioPulse Monitor architecture is approved."

[Assistant]
Verdict: FAIL
Note: The documentation section exhibits repeated project name. The project name 'CardioPulse Monitor' appears excessively. Sentences repeat the same assertion about the cardiac rhythm monitor in different words. Content should be consolidated and each sentence should contribute unique, specific information about the CardioPulse Monitor.


[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 WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

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

[User]
Write a TRACE section on risk control coverage verification for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: The RadOnco Cloud Treatment Planner risk control gap analysis verifies end-to-end traceability per Clause 7.3.2: from hazard to risk control to software requirement to test case to test result. Gaps at any point in this chain prevent release of the Cloud Radiation Treatment Planning SaMD until resolved. The analysis is documented as part of the Release Readiness Review evidence.


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

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

"Formal design reviews with independent reviewers are conducted at each phase gate for the HydroLog. Review findings are tracked to closure."

[Assistant]
Verdict: FAIL
Note: Content mandates formal design reviews with independent reviewers for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent review is required only for Class C.


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

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

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


[System] You are 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 ChestAI Pulmonary Nodule Detector, a Class B AI Pulmonary Nodule Detection SaMD. Reference IEC 62304 Clause 5.1.2.
Cloud AI SaMD analyzing chest CT scans to detect and measure pulmonary nodules, providing CAD overlay for radiologist review. FDA De Novo pathway.

[Assistant] Content: The ChestAI Pulmonary Nodule Detector 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 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 SleepWell (sleep quality display app, Class A):

"Statement coverage of 90% and branch coverage of 80% are mandatory for the SleepWell."

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


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

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

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

[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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-002: "data processing timing constraint" (Category: performance)
Project: VisitorPass Access Management | Visitor Management System | Class A
Visitor registration and temporary badge issuance for hospital access. Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

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

[Assistant]
Description: The VisitorPass Access Management shall process acquired data and update the output within the specified end-to-end latency from sample acquisition to display update.
Rationale: Bounded processing latency ensures the Visitor Management System provides readings reflecting the current state without clinically significant delay.
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 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: "external system data exchange" (Category: interface)
Project: SurgiPlan 3D Surgical Planner | 3D Surgical Planning SaMD | Class B
Preoperative 3D planning of joint replacement procedures with implant sizing and alignment. Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

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 DICOM import, supporting standard message formats.
Rationale: Interoperability enables integration of 3D Surgical Planning SaMD data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User]
Expand requirement SRS-DATA-002: "measurement data lifecycle" (Category: data)
Project: DermaLens Teledermatology Platform | Cloud Teledermatology SaMD | Class B
AI-assisted triage scoring of skin lesion images submitted through a mobile teledermatology workflow. Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

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 DermaLens Teledermatology Platform shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


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

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

"Verification activities follow IEC 62304 Clause 4.4 for performance benchmarking."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 4.4 which does not exist. Clause 4 only has 4.1, 4.2, 4.3. The reference must be corrected to a valid clause number.


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

[User]
Write a SAD section on SOUP component integration and requirements for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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


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

[User]
Write a SDP section on comprehensive deliverables list for Class C for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.1.8.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: Class C documentation for the RetinaStim Visual Prosthesis Controller spans the full IEC 62304 deliverable list. Planning: SDP. Requirements: SRS. Design: SAD and Detailed Design Specification. Verification: unit test report (with coverage >= 90%/80%/80%), integration test report, system test report. Traceability: bidirectional matrix. Risk: complete risk management file. Release: software release record. Each document is independently reviewed.


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

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

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

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


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

[User]
Write a SRS section on operational context and user population for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: This section describes the operational context of the RadOnco Cloud Treatment Planner Cloud Radiation Treatment Planning SaMD. The system is intended for Cloud-based Monte Carlo dose calculation and treatment plan optimization for radiation oncology, operating on AWS p4d GPU instances + EKS + CloudFront. Key interfaces include DICOM RT import/export, REST API, web 3D viewer. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

[User]
Write a SRS section on system boundaries and external dependencies for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clause 5.2.2.
Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

[Assistant] Content: External dependencies of the DermaLens Teledermatology Platform include the Azure Kubernetes Service + CDN operating environment, smartphone camera (via mobile app), and REST API. The Cloud Teledermatology SaMD requirements assume these dependencies operate within their specified parameters; failure modes of external components are addressed in the risk analysis.


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

[User]
Write a FMEA section on risk control measures and implementation for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: Each risk control for the NeoFeed Neonatal Feeding Pump per Clause 7.2.1 specifies the hazard addressed, the control mechanism, and the verification method. Controls implemented in software per Clause 7.2.2 are traced through the requirements-design-test chain to ensure complete implementation and verification in the Neonatal Feeding Pump Firmware.


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

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

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

[Assistant]
Description: Data retention in the AssetTrack Equipment Inventory 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 Equipment Inventory System.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

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

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

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


[System] You are 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 architecture defines three software items with documented interfaces per Clause 5.3.2. Data formats, protocols, and error handling are specified for each interface. SOUP components are identified per Clause 5.3.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PacePilot (pacemaker programmer, Class C). 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 scope boundaries of the software system for RemotICU Continuous Monitoring Hub, a Class B Edge-to-Cloud ICU Monitoring Gateway. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

[Assistant] Content: The RemotICU Continuous Monitoring Hub software boundary includes the application firmware, configuration data, and all SOUP components deployed on Intel NUC edge gateway + AWS IoT Core + React SPA. Hardware components, operating system kernels supplied by the platform vendor, and remote services accessed via REST API are excluded from the software lifecycle activities defined here, though their influence on software behavior is addressed in the risk analysis.


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

"All verification for the cardiac telemetry system follows ISO 14971-1 requirements."

[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 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 PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

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


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

[User]
Write a TRACE section on traceability scope including risk controls for PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: The PathSlide Digital Pathology Viewer 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 Digital Pathology Viewer.


[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: "configurable alarm limits for monitored parameters" (Category: functional)
Project: HandGrip Strength Dynamometer | Hand Dynamometer Firmware | Class B
Measuring hand grip strength and fatigue patterns for rehabilitation progress tracking. Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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

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


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clauses 5.7, 5.7.1.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: Verification of the AutoclaveLog Cycle Recorder consists exclusively of system-level testing per IEC 62304 Clause 5.7. Test cases derive from the software requirements specification and exercise the Sterilization Cycle Data Logger end-to-end on the Windows desktop platform. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are not required for Class A software and are excluded from the verification scope.


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

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

"Traceability is maintained as needed between requirements, design, and test artifacts. Coverage is assessed at appropriate milestones throughout the lifecycle."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed", "appropriate milestones" 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 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 RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clause 5.1.1.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

[Assistant] Content: Milestones governing the RenalDose Renal Adjustment Calculator 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 SDP section on internal SOPs and procedures for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.1.2.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: Company-internal standard operating procedures supplement the international standards for the VitalBoard Patient Summary project. SOP-010 through SOP-013 address development planning, risk management, configuration management, and verification planning. All SOPs are part of the ISO 13485 quality management system and are binding on the Patient Summary Dashboard development team.


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

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

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

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


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

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

"The lifecycle processes for the DialysisGuard comply with ISO 62304."

[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 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 MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

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


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

[User]
Write a SDP section on problem reporting and investigation for LabView Results Portal, a Class A Laboratory Results Viewer. Reference IEC 62304 Clauses 9.1, 9.2.
Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

[Assistant] Content: Software problems discovered during LabView Results Portal development are documented as problem reports per Clause 9.1, including a description of the anomaly, steps to reproduce, and the affected configuration item. Investigation per Clause 9.2 determines the root cause, assesses the impact on previously verified items, and identifies whether the problem affects the safety or effectiveness of the Laboratory Results Viewer.


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

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

"Unit testing for the CaloriePal shall achieve 90% statement coverage and 80% branch coverage."

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


[System] You are an IEC 62304 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 SleepWell (sleep quality display app, Class A):

"The SleepWell 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 StepTrack (wellness pedometer app, Class A):

"Architecture for the StepTrack transforms requirements into a software architecture per Clause 5.3.1. Interfaces between software items are defined per Clause 5.3.2. SOUP functional requirements are specified per Clause 5.3.3. The architecture is verified per Clause 5.3.6."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the StepTrack (wellness pedometer app, Class A). Standards references are accurate.


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

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

[Assistant] Content: Persistent data managed by the WaveReview EEG Archive Viewer includes configuration parameters, acquired measurements from data sources, and operational logs. Data integrity requirements specify error detection mechanisms and the EEG Archive Viewer response to data corruption events.


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

[User]
Write a SDP section on change control and trend analysis for problems for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 9.4, 9.6.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Corrections to the OBDView Diagnostic Display 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 Vehicle Diagnostic Display 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 internal SOPs and procedures for BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clause 5.1.2.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: The BillingBridge Claims Processor 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 FetaSound (fetal heart rate monitor, Class B):

"The FetaSound software development conforms to ISO 62304, with risk management per ISO 14971:2019."

[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 resource constraints and scalability for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clause 5.2.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

[Assistant] Content: Computational resource requirements for the ClinTrial EDC Platform define the maximum CPU utilization, RAM consumption, and flash/disk usage permitted on AWS ECS + RDS PostgreSQL + S3. The Clinical Trial EDC Web Platform must meet all functional and timing requirements within these resource envelopes.


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

"The regulatory framework for the HeartLink references IEC 62304:2006+AMD1:2015 Clauses 4 through 9 as applicable to Class B software. ISO 14971:2019 governs the risk management process. The quality system operates under ISO 13485:2016."

[Assistant]
Verdict: PASS
Note: Content correctly specifies Class B requirements; uses the correct IEC 62304 citation; correctly references ISO 14971:2019. 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 requirements conventions and identification scheme for PharmaSafe CDSS, a Class B Clinical Decision Support System. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Clinical decision support system integrated into hospital EMR providing real-time drug-drug interaction alerts, allergy checking, and dosing guidance.

[Assistant] Content: Requirements for the PharmaSafe CDSS Clinical Decision Support System are documented per Clause 5.2.2 with clear acceptance criteria enabling direct derivation of test cases. Each requirement traces backward to its source and forward to its verification activity in the traceability matrix.


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

[User]
Expand requirement SRS-FUNC-001: "power-on self-test sequence" (Category: functional)
Project: RadView DICOM Viewer | Medical Image Viewer | Class A
Read-only display of medical images for reference viewing. Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

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

[Assistant]
Description: Upon power-up, the RadView DICOM Viewer shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: A power-on self-test confirms hardware and software readiness before the Medical Image Viewer begins use.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

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

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

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


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

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

"Maintenance activities follow IEC 62304-3 Clause 6."

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


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

[User]
Write a SAD section on architecture verification scope for TriageAI Emergency Triage Assistant, a Class B ED Triage Decision Support App. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Tablet app assisting nurses in emergency department triage scoring based on vital signs and presenting symptoms.

[Assistant] Content: This architecture is subject to verification per Clause 5.3.6 before the TriageAI Emergency Triage Assistant proceeds to implementation. Reviewers confirm that the architecture addresses all SRS requirements, interfaces are fully specified, and SOUP items are integrated per Clause 5.3.3.


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

[User]
Expand requirement SRS-SAFE-001: "safe state transition on critical failure" (Category: safety)
Project: NutriCalc TPN Formulation Tool | TPN Formulation Calculator | Class B
Calculating TPN component concentrations and volumes based on nutritional requirements. Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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

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


[System] You are a regulatory 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 operational context and user population for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: This section describes the operational context of the AquaGuard Water Quality Monitor Water Quality Monitoring Firmware. The system is intended for In-situ measurement of water quality parameters for environmental monitoring, operating on MSP430FR (ultra-low-power). Key interfaces include SDI-12, RS-485, solar + battery. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

[User]
Write a SDP section on minimal deliverables list for Class A for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clause 5.1.8.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: The InhaleSense Smart Inhaler Tracker documentation set is limited to the deliverables required for Class A: the SDP, SRS, system test records, software release record, and the risk management file. No architecture document, detailed design specification, unit test report, or integration test report is produced for this Smart Inhaler Adherence Tracker.


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

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

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


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

[User]
Write a SRS section on sensor and communication protocol requirements for WaterPure Quality Logger, a Class A Water Quality Data Logger. Reference IEC 62304 Clause 5.2.2.
Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

[Assistant] Content: External interface requirements for the WaterPure Quality Logger Water Quality Data Logger define the data exchanged across each interface boundary: 4-20mA analog, Modbus RTU. For each interface, requirements specify the protocol, data format, timing, and error recovery behavior.


[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 SleepWell (sleep quality display app, Class A):

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

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


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

[User]
Expand requirement SRS-PERF-002: "resource utilization limits" (Category: performance)
Project: BrachyDose HDR Afterloader Controller | HDR Brachytherapy Afterloader Firmware | Class C
Controlling radioactive source stepping positions and dwell times for high-dose-rate brachytherapy. Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

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 BrachyDose HDR Afterloader Controller shall operate within the specified RAM and flash memory budget on the Dual redundant PLC platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the HDR Brachytherapy Afterloader Firmware, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

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

"Compliance with IEC 62304 Clause Annex B.3 (performance benchmarking) and Clause 5.3.7 (operational qualification) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex B.3 and 5.3.7, neither of which exists. IEC 62304 annexes are not cited as requirements. Clause 5.3 has 5.3.1 through 5.3.6 only. All clause references must be corrected.


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for ConsentView Informed Consent Archive, a Class A Consent Document Viewer. Reference IEC 62304 Clauses 5.7, 5.7.1.
Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

[Assistant] Content: System testing per Clause 5.7 is the sole verification activity for the ConsentView Informed Consent Archive. Tests validate that the Consent Document Viewer meets all specified functional and performance requirements when deployed on Web SPA. Detailed design review (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6) are explicitly not required for this Class A system.


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

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

[Assistant] Content: Timing requirements for the AIDose Chemotherapy Decision Support include end-to-end latency from sensor acquisition to display update, processing throughput for sustained data streams, and startup time. Each timing requirement has a specific numeric bound and is verified through system testing of the Cloud AI Chemotherapy Dosing SaMD.


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

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

"This plan is prepared in compliance with IEC 62311-1 and ISO 13485:2016."

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


[System] You are 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: "Class A scope validation" (Category: safety)
Project: WaveReview EEG Archive Viewer | EEG Archive Viewer | Class A
Read-only playback and display of archived EEG recordings. Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

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

[Assistant]
Description: No software path in the WaveReview EEG Archive Viewer shall control therapeutic outputs, modify diagnostic results, or generate clinical alerts, confirming the validity of the Class A safety classification.
Rationale: The Class A classification of the EEG Archive Viewer depends on the software having no path to contribute to a hazardous situation.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the EEG Archive Viewer.
Source: Regulatory


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

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

"All MedInventory 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 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 TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: SOUP anomaly evaluation for the TransVent Transport Ventilator per Clause 7.1.3 reviews published defect lists for each third-party component. Anomalies that could affect the Transport Ventilator Firmware safety or functionality are documented in the risk management file with corresponding risk control measures.