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

[User]
Write a SDP section on problem reporting and investigation for RemotICU Continuous Monitoring Hub, a Class B Edge-to-Cloud ICU Monitoring Gateway. Reference IEC 62304 Clauses 9.1, 9.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 problem reporting process per Clause 9.1 captures all software anomalies with sufficient detail for reproduction and root cause investigation. Clause 9.2 investigation assesses whether the problem represents a safety risk, determines the affected scope within the Edge-to-Cloud ICU Monitoring Gateway, and identifies the corrective action required.


[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 documenting failure modes and their effects for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Cloud platform enabling dermatologists to review patient-submitted skin images with AI-assisted triage scoring. Images uploaded from mobile app to cloud pipeline.

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


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

[User]
Write a SDP section on risk control requirements traceability for MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clause 5.2.3.
Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

[Assistant] Content: Risk control measures identified in the ISO 14971 risk management process are traced to specific software requirements per Clause 5.2.3. For the MedImage PACS Viewer, this includes controls addressing input data failure modes, communication integrity on DICOMweb WADO-RS, and data validation.


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

[User]
Expand requirement SRS-INTF-001: "primary sensor interface protocol" (Category: interface)
Project: HemaCount Digital Cell Counter | IVD Digital Cell Counter Software | Class B
Automated white blood cell differential counting from digitized peripheral blood smear images. Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

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 HemaCount Digital Cell Counter shall communicate with the microscope camera via USB camera, implementing error detection and recovery for communication failures.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the IVD Digital Cell Counter Software 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 risk control verification and traceability for HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

[Assistant] Content: The HomeVent BiPAP Controller risk control traceability matrix per Clause 7.3.2 links every identified hazard cause to its software-implemented control and to the verification activity confirming its effectiveness. Clause 7.3.3 requires documentation of the verification results for each risk control measure applied to the BiPAP Device Firmware.


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

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

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

[Assistant]
Description: The BreathEasy Air Quality Display shall communicate with the SCD41 CO2 sensor via I2C, implementing error detection and recovery for communication failures.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Environmental Air Quality Display output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

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

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


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

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

"The development plan references IEC 62304 Clause 5.5.6 and Clause 5.3.7 for the DialysisGuard."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.5.6 and 5.3.7, neither of which exists. Clause 5.5 has 5.5.1 through 5.5.5 only. Clause 5.3 has 5.3.1 through 5.3.6 only. All clause references must be corrected.


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

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

[Assistant] Content: Processing requirements for the PharmaSafe CDSS Clinical Decision Support System 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 regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

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

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


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

[User]
Write a SDP section on requirements verification approach for ConveyorGuard Safety Interlock System, a Class A Conveyor Safety Interlock Software. Reference IEC 62304 Clause 5.2.6.
Safety PLC program monitoring conveyor belt guard positions, emergency stops, and light curtains. Functional safety application.

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


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for GasMonitor Anesthetic Gas Logger, a Class A Anesthetic Gas Concentration Logger. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Software logging waste anesthetic gas concentrations in operating rooms for occupational safety compliance. Recording only.

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


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clause 7.1.1.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: The AllergyCard Patient Allergy Viewer FMEA scope is limited to confirmation that no software failure mode contributes to a hazardous situation, consistent with the Class A classification per Clause 7.1.1. The analysis covers data acquisition, processing, and display functions of the Patient Allergy Display and confirms that all failure effects are limited to loss of informational functionality.


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

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

"For the Class A NurseCall Hub, verification is limited to system-level test execution per Clause 5.7. The developer performs verification. No independent review is required. Test records include pass/fail results and defect references."

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

[User]
Write a TRACE section on purpose and scope of the traceability matrix for AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clause 5.7.1.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

[Assistant] Content: Traceability for the AIDose Chemotherapy Decision Support per Clause 5.7.1 links system requirements to software requirements, software requirements to design elements, and design elements to verification test cases. The matrix serves as the primary evidence that the Cloud AI Chemotherapy Dosing SaMD verification is complete and that no requirement is unaddressed.


[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 PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clause 5.2.2.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: Computational resource requirements for the PathSlide Digital Pathology Viewer define the maximum CPU utilization, RAM consumption, and flash/disk usage permitted on Web SPA with WebGL. The Digital Pathology Viewer 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 CaloriePal (nutrition tracking app, Class A):

"MC/DC coverage of 80% is required for all safety-critical modules of the CaloriePal."

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

"Unit testing for the SleepWell shall use mutation testing to ensure test suite effectiveness, targeting a mutation score of at least 85%."

[Assistant]
Verdict: FAIL
Note: Content mandates mutation testing at unit level 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 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 BillingBridge Claims Processor, a Class A Claims Processing Service. Reference IEC 62304 Clause 5.2.2.
Backend service processing insurance claims from the hospital billing system. Financial processing only, no clinical data.

[Assistant] Content: The BillingBridge Claims Processor shall operate within the memory, storage, and processing constraints of the Cloud (AWS) platform. Resource usage requirements are specified with numerical bounds and verified through profiling during system testing of the Claims Processing Service.


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

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

"Class C verification for the RadBeam Planner includes unit testing with statement coverage of at least 90%, branch coverage of at least 80%, and MC/DC coverage of at least 80% for safety-critical modules. Integration testing verifies all inter-unit interfaces. System-level verification is performed by independent personnel."

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


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

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

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

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


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

[User]
Expand requirement SRS-DATA-001: "measurement record integrity" (Category: data)
Project: NeuroTune DBS Programmer | Deep Brain Stimulator Programmer App | Class C
Programming stimulation parameters of implanted deep brain stimulators for Parkinson's disease management. Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

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

[Assistant]
Description: Data integrity of all stored records in the Deep Brain Stimulator Programmer App shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Deep Brain Stimulator Programmer App are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

[User]
Expand requirement SRS-FUNC-003: "initialization integrity checks" (Category: functional)
Project: PainScale Digital Assessment Tool | Pain Assessment Tool | Class B
Standardized pain intensity and quality assessment with longitudinal tracking for treatment evaluation. Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

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: A power-on self-test shall validate primary sensor communication, memory integrity, and web form connectivity before the Pain Assessment Tool transitions to its operational state.
Rationale: Startup verification prevents the Pain Assessment Tool from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[Assistant] Content: Work instructions for the HandGrip Strength Dynamometer are codified in SOPs maintained within the ISO 13485 quality management system. SOP-010 (development planning), SOP-011 (risk management), SOP-012 (configuration management), and SOP-013 (verification) define step-by-step procedures for each IEC 62304 lifecycle activity applicable to the Hand Dynamometer 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 VentAssist Pro (ICU ventilator controller, Class C):

"Architectural design follows IEC 62304:2022 Clause 5.3 for Class C devices."

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


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

[User]
Write a SDP section on verification strategy for Class B -- integration and system testing for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clauses 5.6, 5.6.3, 5.7.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

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


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

[User]
Write a SRS section on purpose of the SRS document for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clause 5.2.1.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

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


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

"IEC 14971 Section 4.3 requires all software units to be verified."

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


[System] You are 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 GlucoTrack CGM (continuous glucose monitor display, Class B):

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the GlucoTrack CGM (continuous glucose monitor display, Class B). Standards references are accurate.


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

[User]
Write a TRACE section on gap identification and coverage analysis for ConsentView Informed Consent Archive, a Class A Consent Document Viewer. Reference IEC 62304 Clause 5.7.4.
Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

[Assistant] Content: The gap analysis for the ConsentView Informed Consent Archive identifies any software requirements without linked test cases, design elements without source requirements (orphan implementations), and test cases that do not trace to any requirement (unnecessary tests). All gaps are documented and resolved before the Release Readiness Review to confirm that the Consent Document Viewer verification is complete per Clause 5.7.4.


[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 format and interoperability requirements for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clause 5.2.2.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: The ThermoWatch Core Temperature Monitor Core Temperature Monitor Firmware data exchange formats are specified in this SRS with field-level definitions, data types, units, and valid ranges. The software performs schema validation on all incoming data from 433 MHz RF before processing.


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

[User]
Write a SRS section on baseline security requirements for HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clause 5.2.2.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: Baseline security requirements for the HeartView Resting HR Display ensure the Heart Rate Display Firmware protects user data, resists unauthorized access, and maintains audit trails. Data communicated via OLED SPI is encrypted. Access is controlled through authentication mechanisms appropriate to the deployment environment.


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

[User]
Expand requirement SRS-SAFE-002: "safety classification confirmation for Class A" (Category: safety)
Project: TrainCert Staff Certification Tracker | Training Certification System | Class A
Tracking and reporting on staff training certifications and renewals. Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

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 Training Certification System software functions are limited to informational display and data presentation, with no capability to influence clinical decisions or therapeutic actions.
Rationale: The Class A classification of the Training Certification System 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 Training Certification System.
Source: Regulatory


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

[User]
Write a SDP section on Class C classification justification and implications for AutoPancreas Closed-Loop Glucose Controller, a Class C Artificial Pancreas Controller Firmware. Reference IEC 62304 Clause 4.3.
Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

[Assistant] Content: Under Clause 4.3, the AutoPancreas Closed-Loop Glucose Controller receives Class C classification. Failure of the Artificial Pancreas Controller Firmware during Automated closed-loop insulin delivery based on continuous glucose monitoring with predictive algorithms poses a direct risk of serious injury. All IEC 62304 development and verification activities apply without exception, and independent technical review is required for requirements, architecture, detailed design, and every level of verification.


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

[User]
Write a SDP section on change control process for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 8.2, 8.2.1.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: The change control procedure for the TrainCert Staff Certification Tracker mandates that every modification to a controlled configuration item is initiated via a change request per Clause 8.2.1. Each request documents the proposed change, safety impact assessment, affected configuration items, and required re-verification for the Training Certification System.


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

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

[Assistant] Content: The HydroRemind Hydration Tracker FMEA scope is limited to confirmation that no software failure mode contributes to a hazardous situation, consistent with the Class A classification per Clause 7.1.1. The analysis covers data acquisition, processing, and display functions of the Hydration Tracking Firmware and confirms that all failure effects are limited to loss of informational functionality.


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

[User]
Expand requirement SRS-FUNC-002: "continuous data sampling from primary sensor" (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: The ConsentView Informed Consent Archive shall continuously sample primary sensor data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Read-only viewing of archived informed consent documents.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Write a SDP section on risk control requirements traceability for IncidentReport Clinical Event Logger, a Class A Incident Reporting System. Reference IEC 62304 Clause 5.2.3.
Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

[Assistant] Content: Software-implemented risk controls for the IncidentReport Clinical Event Logger are documented as explicit requirements per Clause 5.2.3. Traceability from the ISO 14971 risk analysis through the SRS to verification test cases ensures that every risk control measure is implemented and verified in the Incident Reporting System.


[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 WasteTrack Biohazard Logger, a Class A Biohazard Waste Tracking App. Reference IEC 62304 Clauses 5.7, 5.7.1.
Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

[Assistant] Content: The WasteTrack Biohazard Logger 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 Biohazard Waste Tracking App 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 Biohazard Waste Tracking App.


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-003: "electrode impedance measurement data capture and buffering" (Category: functional)
Project: CochleaMap CI Fitting Software | Cochlear Implant Fitting Software | Class C
Programming electrode mapping and stimulation parameters for cochlear implant sound processors. Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

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 CochleaMap CI Fitting Software shall continuously sample electrode impedance measurement data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Programming electrode mapping and stimulation parameters for cochlear implant sound processors.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

[User]
Expand requirement SRS-INTF-003: "external system data exchange" (Category: interface)
Project: AutoHUD Heads-Up Display Controller | Automotive HUD Controller Firmware | Class A
Rendering critical driving information on a windshield heads-up display. Firmware rendering vehicle speed, navigation, and ADAS warnings on a windshield-projected heads-up display.

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 AutoHUD Heads-Up Display Controller shall exchange data with external systems via CAN bus using the specified message format with error handling.
Rationale: Interoperability enables integration of Automotive HUD Controller Firmware data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User] Does IEC 81001-5-1:2021 exist?

[Assistant] Yes. IEC 81001-5-1:2021 covers security in the health software lifecycle. It is harmonized under EU MDR.


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

"This plan is prepared in compliance with ISO 14901 and ISO 13485:2016."

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for ScreenFlow Population Health Screener, a Class A Serverless Population Health Screening SaMD. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

[Assistant] Content: The ScreenFlow Population Health Screener 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 SDP section on development methodology for Class B for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.1.1.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

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


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

[User]
Expand requirement SRS-FUNC-001: "real-time data presentation on REST API" (Category: functional)
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: Output presentation on the REST API shall refresh at the configured interval, reflecting the most recent processed data from the Equipment Inventory System pipeline.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
Source: User need


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

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

[Assistant] Content: Operational context: the CardioLoop Cardiac Resync Controller is a CRT Optimization Firmware used for Real-time optimization of biventricular pacing parameters based on hemodynamic sensor feedback. The software executes on Ultra-low-power ASIC + ARM Cortex-M0 and interfaces with intracardiac impedance for data acquisition. The user population and use environment define the requirements for usability, reliability, and performance.


[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: "record keeping duration" (Category: data)
Project: FleetTrack GPS Tracking Module | Fleet GPS Tracking Firmware | Class A
Real-time GPS tracking and geofence monitoring of fleet vehicles. Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

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 FleetTrack GPS Tracking Module shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Regulatory compliance requires that measurement records be available for the specified retention period.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

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

"Verification of the RadView DICOM is scoped to system testing. The DICOM image viewer cannot contribute to a hazardous situation, so minimal verification consisting of system tests against requirements is sufficient per IEC 62304."

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


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

[User]
Expand requirement SRS-DATA-002: "data retention period" (Category: data)
Project: OBDView Diagnostic Display | Vehicle Diagnostic Display App | Class A
Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use. Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

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

[Assistant]
Description: Measurement records stored by the Vehicle Diagnostic Display App shall be maintained for the configured retention period before eligible for overwrite.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Vehicle Diagnostic Display App.
Priority: Mandatory
Acceptance Criterion: Retention period validation: records created at time T are still accessible at T + retention period.
Source: Regulatory


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

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

[Assistant] Content: The RadOnco Cloud Treatment Planner risk control verification per Clause 7.3.1 exercises each control measure in isolation and in the context of the complete Cloud Radiation Treatment Planning SaMD. Clause 7.3.3 documentation records the verification method, the test result, and the conclusion regarding the control's effectiveness.


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

"Software problem resolution follows ISO 14901 Clause 9."

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


[System] You are 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 requirements elicitation and documentation for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: The CardioCloud ECG Analysis Service software requirements are captured in the SRS per Clause 5.2.1. Sources include system requirements for the Cloud ECG Analysis SaMD, risk control measures from the ISO 14971 analysis, and regulatory requirements from the target markets. Each requirement is verifiable and traceable.


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

[Assistant] Content: The failure mode identification for the WeightAlert Neonatal Scale Neonatal Scale Firmware 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 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):

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

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


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

"Software architecture for the PhysioTrack Rehab is documented per Clause 5.3. The architecture defines software items, their interfaces (Clause 5.3.2), and SOUP requirements (Clause 5.3.3). Integration testing validates the architecture at each integration step."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the PhysioTrack Rehab (rehabilitation tracking system, Class B). Standards references are accurate.


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

[User]
Expand requirement SRS-FUNC-005: "power-on self-test sequence" (Category: functional)
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 LabView Results Portal startup sequence shall include diagnostic checks of all critical subsystems and report any detected faults before allowing operational use.
Rationale: Startup verification prevents the Laboratory Results Viewer from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[User]
Write a SDP section on risk control verification and traceability for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: The BreathSync ICU Ventilator Controller risk control traceability matrix per Clause 7.3.2 links every identified hazard cause to its software-implemented control and to the verification activity confirming its effectiveness. Clause 7.3.3 requires documentation of the verification results for each risk control measure applied to the ICU Ventilator Controller Software.


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

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

"Verification for the StepTrack wellness pedometer app follows Clause 5.7 only. System tests exercise the software in its target configuration. Clause 5.5 unit verification and Clause 5.6 integration testing are explicitly excluded for Class A."

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


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

[User]
Expand requirement SRS-DATA-002: "data retention period" (Category: data)
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 LabView Results Portal shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Laboratory Results Viewer.
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 DialysisGuard (hemodialysis machine controller, Class C):

"Software safety classification is performed per ISO 14901 Clause 4.3."

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


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

[User]
Write a FMEA section on risk control verification for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clauses 7.3.1, 7.3.3.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

[Assistant] Content: Verification of DoseVerify In-Vivo Dosimetry System risk controls per Clause 7.3.1 is performed as part of the applicable verification level for the safety class. Each verified control has a documented result per Clause 7.3.3, confirming the In-Vivo Dosimetry Verification Software meets the risk acceptability 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 THREAT section on STRIDE threat categories applied to the device for TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.2.2.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: The TriagePro Emergency Scoring App threat analysis applies STRIDE to every trust boundary crossing in the Emergency Department Triage SaMD. Each identified threat is rated for impact and likelihood, and mitigation controls are defined. Mitigations are traced to security requirements in the SRS and verified through security testing per IEC 81001-5-1:2021.


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

[User]
Write a SDP section on SOUP identification and management for WaterPure Quality Logger, a Class A Water Quality Data Logger. Reference IEC 62304 Clause 8.1.2.
Embedded system logging purified water system parameters (conductivity, TOC, flow rate) for pharmaceutical manufacturing compliance.

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


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

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

"The NeuroStim Programmer integration test plan addresses Clause 5.6.1 through 5.6.7. Software units are integrated incrementally with testing at each step. Test content per Clause 5.6.4 covers data integrity, timing constraints, and fault tolerance. Test records meet Clause 5.6.7 requirements."

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


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

[User]
Write a SDP section on problem reporting and investigation for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clauses 9.1, 9.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: The CogniTest Cognitive Assessment App problem reporting process per Clause 9.1 captures all software anomalies with sufficient detail for reproduction and root cause investigation. Clause 9.2 investigation assesses whether the problem represents a safety risk, determines the affected scope within the Cognitive Assessment Application, and identifies the corrective action required.


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

[User]
Write a SRS section on functional requirements overview for InfuRate IV Flow Calculator, a Class B Infusion Rate Calculator. Reference IEC 62304 Clause 5.2.2.
Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

[Assistant] Content: This section specifies the functional behavior of the InfuRate IV Flow Calculator Infusion Rate Calculator. Requirements cover data input from external sources, processing algorithms, output generation via desktop GUI, and user interaction patterns. All functional requirements are derived from the system specification or risk analysis.


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

[User]
Write a SDP section on risk management integration into the lifecycle for BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clauses 7.1, 7.1.1.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

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


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

"Applicable standards for the InfuSafe Controller 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 SDP section on acceptance criteria and independent review for Class C for StrokeAlert CT Perfusion Analyzer, a Class C AI Stroke Triage CT Perfusion SaMD. Reference IEC 62304 Clauses 5.5.3, 5.5.5, 5.7.4.
Time-critical cloud SaMD processing CT perfusion scans to generate ischemic core and penumbra maps for acute stroke triage. Results pushed to mobile app within 5 minutes.

[Assistant] Content: The StrokeAlert CT Perfusion Analyzer verification acceptance workflow proceeds bottom-up: unit tests are reviewed first (Clause 5.5.5), followed by integration tests (Clause 5.6.5), and finally system tests (Clause 5.7.4). At each level, an independent reviewer confirms pass/fail results, coverage metrics, and anomaly dispositions. No release of the AI Stroke Triage CT Perfusion SaMD occurs until all levels are signed off.


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

"Referenced standards for the PacePilot 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 SDP section on internal SOPs and procedures for FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clause 5.1.2.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

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


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

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

"Standards compliance for the RadView DICOM DICOM image viewer 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 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"Per IEC 62304, software safety classification is performed. Per IEC 62304, the safety class is determined. Per IEC 62304, the safety classification is documented. Per IEC 62304, the ThermoGuard is classified per IEC 62304."

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


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

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

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

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


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

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

[Assistant] Content: The HydroRemind Hydration Tracker functional requirements define what the Hydration Tracking Firmware does in response to user inputs, sensor data, and system events. Requirements are organized by functional area: data acquisition, signal processing, display and output, and system management. Each requirement is individually testable.


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

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

"IEC 62304-2 Section 6.1 requires all software units to be verified."

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


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

[User]
Write a TRACE section on traceability scope including risk controls for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: The AirSentry Urban Air Quality Station 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 Air Quality Monitoring Station Firmware.


[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: "RAM and storage constraints" (Category: performance)
Project: InfuRate IV Flow Calculator | Infusion Rate Calculator | Class B
Calculating IV infusion rates from prescribed doses, concentrations, and patient parameters. Desktop calculator for IV infusion rates based on drug concentration, patient weight, and ordered dose. Clinical decision support tool.

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 InfuRate IV Flow Calculator shall operate within the specified RAM and flash memory budget on the Windows/macOS desktop platform, including all runtime allocations.
Rationale: Exceeding memory limits could cause undefined behavior in the Infusion Rate Calculator, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


[System] You are a regulatory 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 requirements elicitation and documentation for PulseRing Smart Ring Monitor, a Class B Wearable Smart Ring Firmware + Companion App. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Wearable smart ring firmware measuring continuous PPG for heart rate and SpO2 with BLE streaming to companion mobile app for trend display.

[Assistant] Content: Software requirements for the PulseRing Smart Ring Monitor are derived from system requirements, the risk management file, and stakeholder inputs per Clause 5.2.1. Each requirement specifies functional behavior, performance criteria, or interface constraints relevant to the Wearable Smart Ring Firmware + Companion App and its use in Continuous photoplethysmography-based heart rate and SpO2 monitoring via wearable ring with mobile companion.


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

"Detailed design for the RadView DICOM documents algorithms, data structures, and internal interfaces for each software unit per Clause 5.4.2."

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


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

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

"The RadBeam Planner addresses IEC 62304 Clause 4.4 for user acceptance testing and Clause 5.0 for data archival."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 4.4 and 5.0, neither of which exists. Clause 4 only has 4.1, 4.2, 4.3. Clause 5 starts at 5.1. All clause references must be corrected.


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

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

"Unit testing for the CaloriePal shall use mutation testing to ensure test suite effectiveness, targeting a mutation score of at least 85%."

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


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

[User]
Expand requirement SRS-FUNC-001: "measurement data archival" (Category: functional)
Project: PedDose Pediatric Dosing App | Pediatric Dosing Calculator App | Class B
Weight-based pediatric dose calculations with age-appropriate range checking. Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

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

[Assistant]
Description: All processed measurements shall be stored with timestamps in a persistent log accessible through local drug database for clinical review and regulatory audit.
Rationale: Data logging supports clinical review, trend analysis, and regulatory audit trail requirements for the Pediatric Dosing Calculator App.
Priority: Desirable
Acceptance Criterion: Logged data is retrievable after power cycle, with all timestamps accurate to within 1 second of the reference clock.
Source: User need


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

[User]
Expand requirement SRS-SEC-001: "user identity verification" (Category: security)
Project: HydroRemind Hydration Tracker | Hydration Tracking Firmware | Class A
Passive display of daily water consumption for wellness. Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

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

[Assistant]
Description: User authentication shall be enforced for all configuration changes to the HydroRemind Hydration Tracker, with credential validation before granting access.
Rationale: Unauthorized configuration changes to the Hydration Tracking Firmware could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

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

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


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

[User]
Write a SAD section on data paths and processing pipeline for PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

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


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

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

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

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


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

[User]
Write a THREAT section on system description for threat modeling for NeoFeed Neonatal Feeding Pump, a Class C Neonatal Feeding Pump Firmware. Reference IEC 62304 Clause 5.2.1.
Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

[Assistant] Content: Threat modeling for the NeoFeed Neonatal Feeding Pump begins with a system description identifying entry points, data stores, and trust boundaries of the Neonatal Feeding Pump Firmware. The model covers the STM32L5 (TrustZone) execution environment, all stepper motor driver, I2C display, nurse call interfaces, and persistent data stores.


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

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

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

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


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

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

"The InfuSafe Controller development follows full Class C rigor: detailed design documentation, unit testing with coverage targets (statement 90%, branch 80%, MC/DC 80%), integration testing of all interfaces, system testing, and independent verification. All activities are traceable to requirements."

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


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

[User]
Expand requirement SRS-INTF-002: "data export and interoperability" (Category: interface)
Project: DoseVerify In-Vivo Dosimetry System | In-Vivo Dosimetry Verification Software | Class C
Real-time verification of delivered radiation dose using in-vivo dosimeter measurements during treatment. Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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 DoseVerify In-Vivo Dosimetry System shall exchange data with external systems via electrometer readout using the specified message format with error handling.
Rationale: External system connectivity is required for the In-Vivo Dosimetry Verification Software to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

[User]
Expand requirement SRS-FUNC-005: "continuous data sampling from miniature camera" (Category: functional)
Project: RetinaStim Visual Prosthesis Controller | Retinal Prosthesis Controller Firmware | Class C
Processing camera input and driving retinal implant electrode stimulation patterns for artificial vision. Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

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

[Assistant]
Description: The RetinaStim Visual Prosthesis Controller shall continuously sample miniature camera data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Processing camera input and driving retinal implant electrode stimulation patterns for artificial vision.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

[User]
Write a SDP section on development methodology for Class C with full V-model for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.1.1.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: A rigorous V-model lifecycle governs BeamPlan Radiation Treatment Planner development, providing the verification traceability demanded by Class C software where failure could contribute to serious injury. Each development phase -- requirements, architecture, detailed design, implementation -- has a corresponding verification phase with documented evidence reviewed by independent personnel not involved in the development activity.