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

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

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


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

[User]
Expand requirement SRS-PERF-003: "measurement accuracy specification" (Category: performance)
Project: DialyFlow Dialysis Fluid Controller | Hemodialysis Fluid Controller Firmware | Class C
Controlling dialysate composition, flow rates, and ultrafiltration in hemodialysis. Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

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

[Assistant]
Description: Output accuracy of the Hemodialysis Fluid Controller Firmware shall meet or exceed the specified tolerance for all measurement parameters across operating conditions.
Rationale: Measurement accuracy directly affects clinical decisions based on the Hemodialysis Fluid Controller Firmware output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Accuracy verified against a calibrated reference across the full measurement range, with all readings within tolerance for 200+ test points.
Source: Regulatory


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

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

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

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


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-005: "startup diagnostic verification" (Category: functional)
Project: FetalGuard Heart Rate Monitor | Fetal Heart Rate Monitor Firmware | Class B
Continuous external fetal heart rate monitoring during labor with clinical display. External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

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

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


[System] You are 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 EchoAssist (echocardiogram analysis aid, Class B):

"The EchoAssist 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 EchoAssist (echocardiogram analysis aid, Class B). Standards references are accurate.


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

[User]
Write a SRS section on latency and throughput 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 performance requirements define measurable bounds on processing latency, data throughput, and memory utilization. The Core Temperature Monitor Firmware must sustain these performance levels under peak operating conditions on PIC32MZ throughout the full duration of Continuous core body temperature monitoring with trend display and threshold alerts.


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

"ISO 14971-1 Section 4.3 requires all software units to be verified."

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


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

[User]
Write a SRS section on functional requirements overview for DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: This section specifies the functional behavior of the DialyFlow Dialysis Fluid Controller Hemodialysis Fluid Controller Firmware. Requirements cover data input from conductivity sensors (x2), processing algorithms, output generation via CAN bus, 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SEC-001: "user identity verification" (Category: security)
Project: CleanRoom Particle Counter Logger | Cleanroom Environmental Logger | Class A
Logging and displaying airborne particle counts for cleanroom compliance. Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

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

[Assistant]
Description: Access to configuration and administrative functions of the Cleanroom Environmental Logger shall be restricted to authenticated and authorized users.
Rationale: Unauthorized configuration changes to the Cleanroom Environmental Logger could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


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

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

"The lifecycle processes for the RetinaScan Pro comply with IEC 14971."

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

[User]
Write a SAD section on architectural overview for Class B for AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: The AnticoagCalc INR Dose Adjuster Anticoagulation Dosing Support Tool is structured as a three-tier architecture: data acquisition, processing, and presentation. Interfaces between tiers are defined per Clause 5.3.2 and serve as integration test points. The architecture supports Python/Flask implementation on Web application.


[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 external interface architecture for PhysioTrack Rehabilitation Monitor, a Class B Physical Therapy Tracking System. Reference IEC 62304 Clause 5.3.2.
Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

[Assistant] Content: The PhysioTrack Rehabilitation Monitor architecture isolates external dependencies behind abstraction interfaces per Clause 5.3.2. The BLE 5.0 and cloud API communication interfaces are accessed through adapter modules that translate protocol-specific details into the internal data model of the Physical Therapy Tracking System.


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

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

"Testing ensures quality. Testing validates the software. Testing verifies requirements. Testing confirms functionality. Testing demonstrates compliance. Testing is performed for the PacePilot."

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


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

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

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

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clause 5.1.1.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: The scope of this plan covers the full software lifecycle of the VisitorPass Access Management, a Visitor Management System classified as Safety Class A under IEC 62304 Clause 4.3. Because the software cannot contribute to a hazardous situation, the plan omits detailed design documentation (Clause 5.4), unit verification (Clause 5.5), and integration testing (Clause 5.6), concentrating instead on system-level activities that confirm the Visitor Management System meets its specified requirements.


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

[User]
Write a SRS section on sensor and communication protocol requirements for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clause 5.2.2.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: The RadView DICOM Viewer communication interfaces include DICOM, desktop GUI connecting the Medical Image Viewer to external systems and sensors. Each interface requirement specifies the expected behavior under normal operation and the response to communication failure conditions.


[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 conforms to IEC 62304:2006+AMD1:2015. Safety classification per Clause 4.3 designates this insulin infusion pump controller as Class C. Risk management follows ISO 14971:2019 with guidance from ISO/TR 24971:2020."

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

[User]
Write a SAD section on interface design between software items for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clause 5.3.2.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

[Assistant] Content: The CochleaMap CI Fitting Software Cochlear Implant Fitting Software software item interfaces per Clause 5.3.2 are defined using typed data structures with explicit ownership semantics. Each interface specifies the pre-conditions, post-conditions, and error conditions. Interface compatibility is verified through integration testing per Clause 5.6.


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

[User]
Write a SRS section on external system communication requirements for LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clause 5.2.2.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: Requirements for external system integration with the LinacControl Beam Delivery System specify the API contracts, data formats, and error handling behavior for all outbound communication from the Linear Accelerator Control Software. The software must handle connection timeouts, malformed responses, and authentication failures without affecting safety-relevant functions.


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

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

"The NeuroStim Programmer follows the software lifecycle. The NeuroStim Programmer implements the lifecycle processes. The NeuroStim Programmer adheres to the lifecycle model. The NeuroStim Programmer conforms to the lifecycle framework."

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


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

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

"The lifecycle processes for the AutoDose TPN comply with ISO 13485-2."

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

[User]
Expand requirement SRS-FUNC-005: "initialization integrity checks" (Category: functional)
Project: FactoryTemp Industrial Temperature Monitor | Industrial Temperature Monitoring Firmware | Class A
Continuous monitoring and logging of factory floor temperatures for process control. Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

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

[Assistant]
Description: Upon power-up, the FactoryTemp Industrial Temperature Monitor shall execute a self-test sequence verifying the integrity of the K-type thermocouples (x16) interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Industrial Temperature Monitoring Firmware 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 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

"The software architecture is designed following best engineering practices. Modules are structured to support maintainability and extensibility as needed."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed" provide no project-specific information about the RetinaScan Pro diabetic retinopathy screening AI. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Write a FMEA section on failure mode identification approach for CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

[Assistant] Content: The CleanRoom Particle Counter Logger failure mode identification per Clause 7.1.2 uses a function-by-function analysis of the Cleanroom Environmental Logger. Each software function is examined for potential failure modes: omission, commission, early, late, and value errors. Potential causes per Clause 7.1.2 include design defects, SOUP anomalies per Clause 7.1.3, and environmental factors.


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

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

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

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


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

[User]
Write a SRS section on sensor and communication protocol requirements for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clause 5.2.2.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: External interface requirements for the PostureGuard Desk Monitor Posture Wellness Display Software define the data exchanged across each interface boundary: USB 2.0, Desktop GUI. For each interface, requirements specify the protocol, data format, timing, and error recovery behavior.


[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 configuration identification approach for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clauses 8.1, 8.1.1.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

[Assistant] Content: All artifacts produced during TempWatch Body Temperature Logger development are placed under configuration control per Clause 8.1. Configuration items include source files, build definitions, documentation, test scripts, and SOUP component packages. Each item is uniquely identified by a repository path and immutable revision hash.


[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 error propagation and data integrity in the pipeline for PulmoCheck Spirometry Analyzer, a Class B Spirometry Analysis Software. Reference IEC 62304 Clause 5.3.2.
Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

[Assistant] Content: The PulmoCheck Spirometry Analyzer architecture defines error propagation rules at each interface per Clause 5.3.2. Invalid data from pneumotachograph is detected at the acquisition boundary and does not propagate into processing stages. Each software item validates its inputs and reports errors through a defined error channel in the Spirometry Analysis Software.


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

[User]
Write a FMEA section on risk control measures and implementation for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: Risk control measures for the GlucoSpot Continuous Glucose Display CGM Display App are prioritized per Clause 7.2.1: inherently safe design first, then protective measures in software, then information for safety. Software-implemented controls per Clause 7.2.2 are expressed as verifiable requirements and traced to their originating hazard.


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

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

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

[Assistant]
Description: The IncidentReport Clinical Event Logger software shall not implement any function that could directly control a therapeutic output, modify a diagnostic conclusion, or trigger a clinical alert, consistent with its Class A classification.
Rationale: Confirming the absence of safety-relevant functions validates the Class A classification under IEC 62304 Clause 4.3.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Incident Reporting System.
Source: Regulatory


[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 minimal deliverables list for Class A for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.1.8.
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 documentation set is limited to the deliverables required for Class A: the SDP, SRS, system test records, software release record, and the risk management file. No architecture document, detailed design specification, unit test report, or integration test report is produced for this Air Quality Monitoring Station Firmware.


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

[User]
Write a SDP section on system test execution and acceptance for Class A for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clauses 5.7, 5.7.4.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: The AllergyCard Patient Allergy Viewer system test suite runs on Web kiosk (Chrome kiosk mode) exercising all functional, performance, and interface requirements. Clause 5.7.4 verification confirms every SRS requirement has at least one passing system test. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are outside the scope of Class A verification and are not executed.


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

[User]
Expand requirement SRS-FUNC-001: "display update rate for Cloud SaMD Histopathology Analysis Platform" (Category: functional)
Project: PathCloud AI Histology Analyzer | Cloud SaMD Histopathology Analysis Platform | Class B
AI-assisted identification of suspicious regions in digitized histology slides for pathologist review. Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

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

[Assistant]
Description: Output presentation on the REST API shall refresh at the configured interval, reflecting the most recent processed data from the Cloud SaMD Histopathology Analysis Platform 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-PERF-003: "measurement accuracy specification" (Category: performance)
Project: AIDose Chemotherapy Decision Support | Cloud AI Chemotherapy Dosing SaMD | Class C
AI-generated chemotherapy dose adjustment recommendations based on patient-specific pharmacogenomic and clinical data. Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

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

[Assistant]
Description: The AIDose Chemotherapy Decision Support shall maintain measurement accuracy within the specified tolerance across the full operating range of the primary sensor.
Rationale: Measurement accuracy directly affects clinical decisions based on the Cloud AI Chemotherapy Dosing SaMD output and is a key factor in the risk profile.
Priority: Mandatory
Acceptance Criterion: Statistical analysis of 500 measurements shows mean error within tolerance and standard deviation within specified limits.
Source: Regulatory


[System] You are 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 RoomBoard Digital Signage, a Class A Patient Room Digital Signage. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Hospital room digital signage displaying patient name, care team, and daily schedule. Display-only, no clinical data entry.

[Assistant] Content: Failure mode documentation for the RoomBoard Digital Signage per Clause 7.1.4 captures the complete chain from cause to effect for each identified failure. The FMEA worksheet records the affected function, failure mode, potential causes, effects on the Patient Room Digital Signage user, and current detection mechanisms.


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

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

"The lifecycle processes for the VentAssist Pro comply with ISO 14901."

[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 milestones and phase transition criteria for RetinaStim Visual Prosthesis Controller, a Class C Retinal Prosthesis Controller Firmware. Reference IEC 62304 Clause 5.1.1.
Firmware driving a retinal implant electrode array based on camera input processing. Stimulation errors could cause retinal damage.

[Assistant] Content: Transition between lifecycle phases requires completion of all phase-gate deliverables and sign-off by the designated reviewers. For the RetinaStim Visual Prosthesis Controller project, key milestones include the Software Requirements Baseline (all requirements reviewed and traced to system requirements), the Design Freeze (architecture and interfaces finalized), and the Release Readiness Review (all verification complete and anomalies dispositioned).


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

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

[Assistant] Content: Hazard identification for the AllergyCard Patient Allergy Viewer per Clause 7.1.2 considers all software functions that could contribute to patient harm. Identified causes include incorrect sensor data processing, loss of communication on HL7 FHIR AllergyIntolerance API, and failure to detect out-of-range conditions during Read-only display of patient allergy information at point of care.


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

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clause 5.1.1.
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: For the MedImage PACS Viewer, this SDP defines a streamlined development process aligned with the Class A requirements of IEC 62304. The Web PACS Image Viewer is used for Web-based display and annotation of DICOM medical images for radiologist review, presenting no pathway to patient harm. Deliverables are limited to the SDP itself, a Software Requirements Specification, system test records, and the software release package. No architecture document, detailed design, or unit test reports are produced.


[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 TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: Risk evaluation of SOUP in the TrainCert Staff Certification Tracker follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Training Certification System. Anomalies relevant to Tracking and reporting on staff training certifications and renewals are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

[User]
Write a SRS section on baseline security requirements for TrainCert Staff Certification Tracker, a Class A Training Certification System. Reference IEC 62304 Clause 5.2.2.
Web app tracking staff training certifications and renewal dates. Administrative HR tool for compliance tracking.

[Assistant] Content: Baseline security requirements for the TrainCert Staff Certification Tracker ensure the Training Certification System protects user data, resists unauthorized access, and maintains audit trails. Data communicated via email notifications is encrypted. Access is controlled through authentication mechanisms appropriate to the deployment environment.


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

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

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

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


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

[Assistant] Content: The MedRef Clinical Reference App development environment consists of Kotlin (Android) + Swift (iOS) targeting iOS/Android native, with version-controlled source and automated builds. Tool qualification per Clause 5.1.4 is not mandated for Class A software. Any tool defects affecting the Clinical Drug Reference App output are documented in the problem report system.


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

[User]
Expand requirement SRS-FUNC-005: "real-time data presentation on BNC input" (Category: functional)
Project: VibeCheck Vibration Analyzer | Vibration Analysis Instrument Firmware | Class A
Vibration spectrum analysis of industrial machinery for predictive maintenance. Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

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

[Assistant]
Description: The VibeCheck Vibration Analyzer display shall present current readings on BNC input within the specified maximum update latency.
Rationale: Display freshness is critical for the Vibration Analysis Instrument Firmware to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


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

[User]
Write a SDP section on system test execution and acceptance for Class A for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clauses 5.7, 5.7.4.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

[Assistant] Content: Acceptance of the AquaGuard Water Quality Monitor is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Water Quality Monitoring 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 PacePilot (pacemaker programmer, Class C):

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

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


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-001: "primary sensor data capture and buffering" (Category: functional)
Project: AllergyCard Patient Allergy Viewer | Patient Allergy Display | Class A
Read-only display of patient allergy information at point of care. Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

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 AllergyCard Patient Allergy Viewer software shall acquire primary sensor data at the specified sampling rate and store values in a circular buffer for processing by the Patient Allergy Display signal pipeline.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Read-only display of patient allergy information at point of care.
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 problem reporting and investigation for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clauses 9.1, 9.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

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


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

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

[Assistant] Content: Software-implemented risk controls for the PainScale Digital Assessment Tool 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 Pain Assessment Tool.


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

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

"The OxyPure Controller configuration management plan identifies all configuration items per Clause 8.1.1. SOUP items are tracked per Clause 8.1.2. Change control follows Clause 8.2 with traceability per Clause 8.2.4. Configuration status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the OxyPure Controller (oxygen concentrator controller, 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 ChemoCalc (chemotherapy dose calculator, Class C):

"Compliance with IEC 62304 Clause 7.5 (operational qualification) and Clause 5.0 (continuous monitoring) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 7.5 and 5.0, neither of which exists. Clause 7 ends at 7.4. 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 MedInventory (medical supply tracking system, Class A):

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

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

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

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


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

[User]
Write a TRACE section on risk control coverage verification for CardioRhythm ECG Analyzer, a Class B Single-Lead ECG Device Firmware. Reference IEC 62304 Clauses 5.7.4, 7.3.2.
Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay diagnosis.

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


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

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the OxyPure Controller (oxygen concentrator controller, Class C). Standards references are accurate.


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

[User]
Write a SRS section on resource constraints and scalability for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clause 5.2.2.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: The PostureGuard Desk Monitor resource constraints are derived from the Windows/macOS desktop hardware capabilities. Requirements specify headroom margins for memory and processing to ensure the Posture Wellness Display Software remains stable under sustained operation during Visual feedback on desk posture for personal wellness awareness.


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

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

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

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


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

[User]
Expand requirement SRS-SEC-002: "patient data protection" (Category: security)
Project: BreathSync ICU Ventilator Controller | ICU Ventilator Controller Software | Class C
Automated mechanical ventilation with multiple modes, alarm management, and patient synchronization. Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

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

[Assistant]
Description: All stored patient data in the ICU Ventilator Controller Software shall be protected by AES-256 or equivalent encryption, with keys managed per established cryptographic practices.
Rationale: Encryption of stored patient data protects against unauthorized disclosure if the ICU Ventilator Controller Software storage media is accessed outside the intended context.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

[User]
Expand requirement SRS-INTF-002: "primary sensor interface protocol" (Category: interface)
Project: WasteTrack Biohazard Logger | Biohazard Waste Tracking App | Class A
Logging and tracking biohazard waste container chain of custody. Mobile app scanning and logging biohazard waste container pickups. Tracks chain of custody for environmental compliance.

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

[Assistant]
Description: Communication with the camera barcode scanner over REST API shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Biohazard Waste Tracking App data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


[System] You are a 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: "primary sensor data capture and buffering" (Category: functional)
Project: MedImage PACS Viewer | Web PACS Image Viewer | Class A
Web-based display and annotation of DICOM medical images for radiologist review. Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

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 MedImage PACS Viewer 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 Web-based display and annotation of DICOM medical images for radiologist review.
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 milestones and phase transition criteria for PowerTrack UPS Monitor, a Class A UPS Monitoring Software. Reference IEC 62304 Clause 5.1.1.
Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

[Assistant] Content: Transition between lifecycle phases requires completion of all phase-gate deliverables and sign-off by the designated reviewers. For the PowerTrack UPS Monitor project, key milestones include the Software Requirements Baseline (all requirements reviewed and traced to system requirements), the Design Freeze (architecture and interfaces finalized), and the Release Readiness Review (all verification complete and anomalies dispositioned).


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

[User]
Write a SDP section on system test execution and acceptance for Class A for HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clauses 5.7, 5.7.4.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

[Assistant] Content: The HumidityMap Room Condition Logger system test suite runs on ESP32 + cloud exercising all functional, performance, and interface requirements. Clause 5.7.4 verification confirms every SRS requirement has at least one passing system test. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are outside the scope of Class A verification and are not executed.


[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 LabStream LIS Middleware, a Class A Laboratory Information Middleware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

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


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

"For the Class A StepTrack, 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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SAD section on purpose of the architecture document for LinacControl Beam Delivery System, a Class C Linear Accelerator Control Software. Reference IEC 62304 Clause 5.3.1.
Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

[Assistant] Content: This SAD transforms the LinacControl Beam Delivery System software requirements into a design architecture per Clause 5.3.1. The Linear Accelerator Control Software is decomposed into software items with clearly defined boundaries, interfaces, and data flows, supporting both implementation and verification activities.


[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 CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 5.2.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: This section describes the operational context of the CogniTest Cognitive Assessment App Cognitive Assessment Application. The system is intended for Administering and scoring standardized cognitive screening tests for clinical neuropsychological assessment, operating on iPadOS. Key interfaces include local database, PDF export. These contextual factors drive the functional and non-functional requirements specified in subsequent sections.


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

[User]
Write a SDP section on development tools and tool qualification for Class A for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clause 5.1.4.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: For the Class A WaveReview EEG Archive Viewer, the development environment comprises Python/PyQt with standard build tooling on Windows/Linux desktop. All source artifacts are version-controlled. Formal tool validation is not required at this classification level; tool versions are recorded in the configuration baseline for reproducibility.


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

[User]
Expand requirement SRS-SEC-001: "access control and authorization" (Category: security)
Project: HandGrip Strength Dynamometer | Hand Dynamometer Firmware | Class B
Measuring hand grip strength and fatigue patterns for rehabilitation progress tracking. Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

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

[Assistant]
Description: Access to configuration and administrative functions of the Hand Dynamometer Firmware shall be restricted to authenticated and authorized users.
Rationale: Access control prevents unauthorized modification of the Hand Dynamometer Firmware operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

[User]
Expand requirement SRS-DATA-002: "stored data corruption detection" (Category: data)
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: The HydroRemind Hydration Tracker shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Corrupted data must be identified to prevent clinical decisions based on unreliable measurements.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

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

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

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


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

[User]
Write a SAD section on architectural overview for Class B for PulseRing Smart Ring Monitor, a Class B Wearable Smart Ring Firmware + Companion App. Reference IEC 62304 Clauses 5.3.1, 5.3.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: The PulseRing Smart Ring Monitor Wearable Smart Ring Firmware + Companion App is structured as a three-tier architecture: data acquisition, processing, and presentation. Interfaces between tiers are defined per Clause 5.3.2 and serve as integration test points. The architecture supports C (firmware) + Swift/Kotlin (companion app) implementation on nRF5340 (firmware) + iOS/Android (app).


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

[User]
Expand requirement SRS-SEC-002: "cryptographic data security" (Category: security)
Project: SurgiPlan 3D Surgical Planner | 3D Surgical Planning SaMD | Class B
Preoperative 3D planning of joint replacement procedures with implant sizing and alignment. Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

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

[Assistant]
Description: Patient-identifiable data stored by the SurgiPlan 3D Surgical Planner shall be encrypted at rest using a validated cryptographic algorithm with a key length of at least 256 bits.
Rationale: Data-at-rest encryption is required to meet privacy regulations and protect patient confidentiality.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

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

"The RadView DICOM detailed design describes algorithms, data structures, and internal interfaces for each unit."

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


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

[User] Is ISO 14901 the correct reference for medical device compliance?

[Assistant] No. ISO 14901 does not exist as a medical device standard. The risk management standard is ISO 14971:2019.


[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 ArthroNav (surgical navigation system, Class C):

"Hazard analysis for the ArthroNav identifies that incorrect display of measurement values could mislead the clinician. Risk control measures include input validation (REQ-SRS-023), display range checking, and a visual indicator when data is stale. Residual risk is acceptable per the risk management plan."

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


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

[User]
Write a SRS section on system boundaries and external dependencies for RetinaScan Diabetic Retinopathy Screener, a Class B Retinal Screening Software. Reference IEC 62304 Clause 5.2.2.
Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist review.

[Assistant] Content: The RetinaScan Diabetic Retinopathy Screener software boundary encompasses the Retinal Screening Software application executing on Windows desktop with GPU. External dependencies include fundus camera DICOM input hardware and desktop GUI. These external systems are treated as black boxes at the software boundary, with interface requirements specified in this SRS.


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

[User]
Write a THREAT section on STRIDE mitigations traced to requirements for WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.2.3.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

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


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

[Assistant] Content: The AnesBot Automated Anesthesia Controller risk control verification per Clause 7.3.1 exercises each control measure in isolation and in the context of the complete Automated Anesthesia Delivery Software. 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 CardioPulse Monitor (cardiac rhythm monitor, Class B):

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the CardioPulse Monitor (cardiac rhythm monitor, Class B). 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 WoundTrack (wound measurement imaging system, Class B):

"Software development follows IEC 62304 Clause 5.8.9 requirements for post-market surveillance."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.8.9 which does not exist. Clause 5.8 has 5.8.1 through 5.8.8 only. The reference must be corrected to a valid clause number.


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

[User]
Write a SRS section on functional requirements overview for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clause 5.2.2.
Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

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

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

"Software development follows IEC 62304 Clause 5.9 requirements for deployment validation."

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


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

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

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

[Assistant]
Description: Upon power-up, the SurgLog Procedure Documentation App shall execute a self-test sequence verifying the integrity of the tablet microphone interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Surgical Documentation App from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


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

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

[Assistant] Content: The DoseCalc Medication Calculator receives a Class B safety classification per IEC 62304 Clause 4.3 because the Medication Dose Calculator App can contribute to a hazardous situation, but external risk controls -- including clinician oversight and independent hardware safety mechanisms -- prevent the hazard from resulting in serious injury. Lifecycle activities required at Class B include architectural design (Clause 5.3), integration testing (Clause 5.6), and system testing (Clause 5.7).


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

[User] What sub-clauses exist under IEC 62304 Clause 5.3?

[Assistant]
IEC 62304 Clause 5.3 (Software architectural design) contains the following sub-clauses:

- Clause 5.3: Software architectural design
- Clause 5.3.1: Transform software requirements into an architecture
- Clause 5.3.2: Develop an architecture for the interfaces of software items
- Clause 5.3.3: Specify functional and performance requirements of SOUP item
- Clause 5.3.4: Specify system hardware and software required by SOUP item
- Clause 5.3.5: Identify segregation necessary for risk control
- Clause 5.3.6: Verify software architecture

These are the only valid sub-clauses under 5.3. No additional sub-clauses exist.


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

"IEC 62304 Clause 5.9 requires the ThermoGuard to implement security testing."

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


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

[User]
Expand requirement SRS-DATA-002: "stored data corruption detection" (Category: data)
Project: StepSync Activity Tracker | Wellness Activity Display App | Class A
Passive display of physical activity metrics for personal wellness tracking. Mobile app displaying daily step count, distance, and calories from a wrist-worn accelerometer. Read-only display with no clinical interpretation.

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 Wellness Activity Display App shall be verified using CRC or equivalent checksums upon read-back.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Wellness Activity Display 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 a regulatory documentation specialist writing IEC 62304:2006+AMD1:2015 compliant medical device software documentation. Generate precise, project-specific content. Use only valid IEC 62304 clause numbers. IEC 62304 is a single-part standard with no sub-parts. Vary your sentence structure and openings. Be specific to the project described — never use generic filler like 'as appropriate' or 'as needed'.

[User]
Write a SDP section on milestones and phase transition criteria for AIDose Chemotherapy Decision Support, a Class C Cloud AI Chemotherapy Dosing SaMD. Reference IEC 62304 Clause 5.1.1.
Cloud SaMD providing AI-driven chemotherapy dosing recommendations based on patient genomics, lab values, and treatment response data.

[Assistant] Content: The AIDose Chemotherapy Decision Support development schedule is anchored to formal milestones with documented transition criteria. Progress is measured against these gates rather than calendar dates, ensuring the Cloud AI Chemotherapy Dosing SaMD meets all quality and safety requirements before advancing to the next lifecycle phase.


[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 enhanced security for Class B and C for RetinaScan Diabetic Retinopathy Screener, a Class B Retinal Screening Software. Reference IEC 62304 Clause 5.2.2.
Desktop software analyzing retinal fundus images to detect signs of diabetic retinopathy for ophthalmologist review.

[Assistant] Content: Enhanced security requirements for the RetinaScan Diabetic Retinopathy Screener address the elevated risk profile of the Retinal Screening Software. Requirements include secure boot verification, integrity checking of critical data structures, tamper detection on DICOM, and a defined vulnerability response process per IEC 81001-5-1:2021.


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

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

[Assistant]
Description: A deterministic safe-state transition shall be triggered by any detected critical fault condition in the InsuPrecise Insulin Pump Controller, with all active outputs brought to a known safe configuration.
Rationale: Fail-safe behavior is essential to prevent the Insulin Pump Controller Firmware from causing harm when its software detects an unrecoverable error.
Priority: Mandatory
Acceptance Criterion: Safe state transition completes within the specified time limit for each defined critical fault, verified by fault injection during operation.
Source: Risk control


[System] You are a regulatory 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 A classification justification and implications for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clause 4.3.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

[Assistant] Content: Safety classification of the TempWatch Body Temperature Logger was performed per IEC 62304 Clause 4.3 and documented in the risk management file. The analysis concluded that the Temperature Logging Firmware is Class A: no identified software failure mode contributes to a hazardous situation. The classification is based on the informational-only nature of Passive logging and display of skin temperature trends for personal interest and the absence of any closed-loop control capability.


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

[User]
Write a SDP section on primary international standards applicable to development for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clause 5.1.2.
Cloud-hosted SaMD analyzing whole-slide histology images with deep learning to flag suspicious regions for pathologist review. Runs as a multi-tenant SaaS.

[Assistant] Content: Development of the PathCloud AI Histology Analyzer software conforms to IEC 62304:2006+AMD1:2015 for the software lifecycle and ISO 14971:2019 for risk management integration. Quality management activities follow ISO 13485:2016, while usability engineering principles from IEC 62366-1:2015+AMD1:2020 inform the user interface design of the Cloud SaMD Histopathology Analysis Platform.


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

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

"The HydroLog addresses IEC 62304 Clause 5.5.2.1 (operational qualification) through formal review."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.5.2.1 which does not exist. IEC 62304 has no four-level numbering. The reference must be corrected to a valid clause number.