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

[User]
Expand requirement SRS-PERF-002: "resource utilization limits" (Category: performance)
Project: AuditTrail QMS Event Logger | QMS Audit Trail Service | Class A
Capturing and archiving QMS events for regulatory audit trails. Microservice capturing and storing quality management system audit events. Logging and reporting only.

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

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


[System] You are a regulatory 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 TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

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


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

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

[Assistant] Content: Risk control verification for the NeoFeed Neonatal Feeding Pump per Clause 7.3.1 confirms that each control is correctly implemented and effective. Test cases exercise the control under normal and boundary conditions. Verification evidence per Clause 7.3.3 links the test result to the risk control measure and the originating hazard in the Neonatal Feeding Pump Firmware risk management file.


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

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

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

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


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

[User]
Expand requirement SRS-INTF-001: "data export and interoperability" (Category: interface)
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: The BreathSync ICU Ventilator Controller shall exchange data with external systems via solenoid valve drivers using the specified message format with error handling.
Rationale: External system connectivity is required for the ICU Ventilator Controller Software to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

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

"Hazard analysis for the LabView Portal 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 SDP section on requirements elicitation and documentation for PhysioTrack Rehabilitation Monitor, a Class B Physical Therapy Tracking System. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

[Assistant] Content: Requirements for the PhysioTrack Rehabilitation Monitor are elicited from system-level specifications, the ISO 14971 risk management file, and user needs analysis. Each software requirement is documented per Clause 5.2.2 with a unique identifier, rationale, acceptance criteria, and traceability to its source.


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

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

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


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

[User]
Write a SDP section on tool qualification for Class B and C for NeuroTune DBS Programmer, a Class C Deep Brain Stimulator Programmer App. Reference IEC 62304 Clause 5.1.4.
Tablet application programming deep brain stimulation implants for movement disorders. Stimulation parameter errors could cause neurological harm.

[Assistant] Content: The C# (Xamarin) compiler, test framework, and coverage analysis tools used for the NeuroTune DBS Programmer are qualified per Clause 5.1.4. Qualification includes comparison of tool output against known-correct reference results and documentation of tool version, configuration, and any known limitations affecting the Deep Brain Stimulator Programmer App verification.


[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: LabStream LIS Middleware | Laboratory Information Middleware | Class A
Routing and auto-validating laboratory results between analyzers and the laboratory information system. Middleware software connecting laboratory analyzers to the hospital LIS. Routes results, applies auto-validation rules, and flags critical values.

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

[Assistant]
Description: Access to configuration and administrative functions of the Laboratory Information Middleware shall be restricted to authenticated and authorized users.
Rationale: Access control prevents unauthorized modification of the Laboratory Information Middleware operating parameters.
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 ThermoGuard (body temperature logger, Class A):

"All interface points between ThermoGuard modules are covered by integration test cases."

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

"Per IEC 62304 Clause 5.1.1, the InfuSafe Controller development plan defines the development process. Per IEC 62304 Clause 5.1.1, this plan establishes development activities. Per IEC 62304 Clause 5.1.1, the software development is governed by this plan. Per IEC 62304 Clause 5.1.1, all development follows this plan."

[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 InfuSafe Controller.


[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 platform and build infrastructure for SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clause 5.1.4.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

[Assistant] Content: Source code for the SleepScore Apnea Screening Tool Sleep Apnea Screening App is written in Swift + Python (backend) and compiled for iOS + cloud. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


[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 lifecycle processes for the OxyPure Controller comply with ISO 13485-1."

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


[System] You are a regulatory 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 test strategy for the MedInventory is limited to system-level verification. All requirements from the SRS are covered by system test cases per Clause 5.7.1. Test failures are managed through the software problem resolution process (Clause 9). Unit and integration testing are out of scope for this Class A medical supply tracking system."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. 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 GlucoTrack CGM (continuous glucose monitor display, Class B):

"The GlucoTrack CGM risk management file documents all identified hazards, estimated risks, implemented controls, and residual risk evaluations. Software-implemented controls are verified through targeted test cases. Verification records per Clause 7.3.3 confirm each control measure functions as intended."

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

[User]
Write a SRS section on baseline security requirements for GasMonitor Anesthetic Gas Logger, a Class A Anesthetic Gas Concentration Logger. Reference IEC 62304 Clause 5.2.2.
Software logging waste anesthetic gas concentrations in operating rooms for occupational safety compliance. Recording only.

[Assistant] Content: Security requirements for the GasMonitor Anesthetic Gas Logger address authentication, data protection, and access control for the Anesthetic Gas Concentration Logger. All persistent data is encrypted at rest, and data in transit over database uses transport layer encryption. Security requirements are aligned with IEC 81001-5-1:2021.


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

[User]
Write a FMEA section on failure mode identification approach for RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

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


[System] You are 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 HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clause 4.3.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

[Assistant] Content: Under IEC 62304 Clause 4.3, the HumidityMap Room Condition Logger is classified as Safety Class A. The Environmental Condition Logger is a purely informational system for Monitoring and logging temperature/humidity in hospital storage areas with no control over therapeutic delivery, diagnostic decision-making, or life-sustaining functions. Software failure would result in loss of informational display, not patient harm.


[System] You are an IEC 62304 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 PowerTrack UPS Monitor, a Class A UPS Monitoring Software. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

[Assistant] Content: Documentation of PowerTrack UPS Monitor failure modes follows Clause 7.1.4. Each entry in the FMEA register includes: the software item, the failure mode, the potential cause(s), the effect on the UPS Monitoring Software during Logging and displaying UPS status for facility infrastructure monitoring, severity and probability ratings, and references to applicable risk control measures.


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

[User]
Expand requirement SRS-INTF-001: "external system data exchange" (Category: interface)
Project: SunGuard UV Index Display | UV Exposure Display Firmware | Class A
Passive display of UV index for personal awareness. Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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

[Assistant]
Description: Data interoperability with clinical information systems shall be provided through I2C, supporting standard message formats.
Rationale: External system connectivity is required for the UV Exposure Display Firmware to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

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

"MISRA C compliance and unit testing with MC/DC coverage are mandatory for the CaloriePal."

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


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

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

"Formal code inspections by independent reviewers are required for all NurseCall Hub source code. Each module shall have unit tests with full branch coverage."

[Assistant]
Verdict: FAIL
Note: Content mandates independent code review and unit testing for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent review and unit testing are not required for Class A 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 SRS section on system boundaries and external dependencies 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 system overview identifies all external entities interacting with the Medical Image Viewer: input sources (external data), output destinations (desktop GUI), and the Windows/macOS/Linux desktop execution environment. Requirements for each external interface are documented in the interface requirements section.


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

[User]
Write a SAD section on SOUP component integration and requirements for DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: Third-party software components used in the DialyFlow Dialysis Fluid Controller are documented per Clause 5.3.3, including functional and performance requirements imposed on each SOUP item. Hardware and software dependencies per Clause 5.3.4 are recorded to ensure that the Dual ARM Cortex-R5 (lockstep + checker) environment satisfies all SOUP prerequisites.


[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 software architecture per Clause 5.3 decomposes the system into software items with documented interfaces."

[Assistant]
Verdict: FAIL
Note: Content mandates architectural design documentation for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Architectural design (Clause 5.3) 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 Class A classification justification and implications for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 4.3.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

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


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

"Risk control measures are implemented per IEC 62304-1 Clause 7."

[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 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 platform and build infrastructure for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.1.4.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The HemaCount Digital Cell Counter build environment uses Python (OpenCV + PyTorch) + C++ (image pipeline) on Windows desktop with GPU. Continuous integration builds execute on every commit, ensuring early detection of compilation errors and regression failures. Toolchain versions are locked to the configuration baseline and recorded in the Software Configuration Management Plan.


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

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

[Assistant] Content: The BeamPlan Radiation Treatment Planner software requirements are captured in the SRS per Clause 5.2.1. Sources include system requirements for the Radiation Treatment Planning Software, risk control measures from the ISO 14971 analysis, and regulatory requirements from the target markets. Each requirement is verifiable and traceable.


[System] You are a regulatory 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 BloodBank Manager (blood bank inventory system, Class A):

"Software problem resolution follows IEC 62304-2 Clause 9."

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


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

"Maintenance planning for the MedInventory is established per Clause 6.1. Problem and modification analysis follows Clause 6.2. Modifications are implemented per Clause 6.3 using the established development processes."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the MedInventory (medical supply tracking system, Class A). 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.2, requirements are defined. Per IEC 62304 Clause 5.2, requirements are documented. Per IEC 62304 Clause 5.2, requirements are analyzed. Per IEC 62304 Clause 5.2, requirements are verified."

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

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

[Assistant] Content: The DoseLog Radiation Badge Reader data format requirements ensure interoperability with external systems connected via USB, database. Data structures, encoding schemes, and byte ordering are fully specified. The Dosimetry Data Logger handles version mismatches in data formats gracefully.


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

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

"Unit verification for the RadBeam Planner follows Clause 5.5. Each unit has acceptance criteria per Clause 5.5.3 and additional criteria per Clause 5.5.4. Verification demonstrates MC/DC coverage for modules identified as safety-critical in the risk analysis."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the RadBeam Planner (radiation therapy planning system, 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 SAD section on purpose of the architecture document for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 5.3.1.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: This Software Architecture Document describes the structural design of the CogniTest Cognitive Assessment App, decomposing the Cognitive Assessment Application into software items with defined interfaces and responsibilities per IEC 62304 Clause 5.3.1. The architecture addresses safety requirements, performance constraints, and integration needs identified in the SRS.


[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 FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clause 5.2.2.
Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

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


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

[User]
Write a SRS section on purpose of the SRS document for CleanRoom Particle Counter Logger, a Class A Cleanroom Environmental Logger. Reference IEC 62304 Clause 5.2.1.
Software collecting particle count data from cleanroom sensors. Logs and charts data for environmental monitoring compliance.

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


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

[Assistant] Content: The change control procedure for the InfuRate IV Flow Calculator mandates that every modification to a controlled configuration item is initiated via a change request per Clause 8.2.1. Each request documents the proposed change, safety impact assessment, affected configuration items, and required re-verification for the Infusion Rate Calculator.


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

[User]
Write a SDP section on risk control verification and traceability for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: Risk control measures in the BrachyDose HDR Afterloader Controller are verified per Clause 7.3.1 through the testing activities appropriate to the safety classification. Traceability per Clause 7.3.2 links each identified hazard to its risk control measure, the software requirement implementing the control, and the test case verifying the control's effectiveness in the HDR Brachytherapy Afterloader 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 requirements verification approach for SterilLog Sterilization Record System, a Class A Sterilization Record Logger. Reference IEC 62304 Clause 5.2.6.
Software logging sterilization cycle parameters from autoclaves. Records temperature, pressure, and time for compliance documentation.

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


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

[User]
Write a SDP section on internal SOPs and procedures for AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clause 5.1.2.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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


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

[User]
Write a SAD section on SOUP component integration and requirements for PharmLog Medication History Viewer, a Class A Medication History Viewer. Reference IEC 62304 Clauses 5.3.3, 5.3.4.
Mobile app displaying a patient's medication history from the pharmacy system. Read-only with no prescribing or interaction checking.

[Assistant] Content: Third-party software components used in the PharmLog Medication History Viewer are documented per Clause 5.3.3, including functional and performance requirements imposed on each SOUP item. Hardware and software dependencies per Clause 5.3.4 are recorded to ensure that the iOS environment satisfies all SOUP prerequisites.


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

"Hazard analysis for the PacePilot 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 compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"Formal code inspections by independent reviewers are required for all RadView DICOM source code. Each module shall have unit tests with full branch coverage."

[Assistant]
Verdict: FAIL
Note: Content mandates independent code review and unit testing for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Independent review and unit testing are not required for Class A 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 SDP section on Class A classification justification and implications for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clause 4.3.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: Under IEC 62304 Clause 4.3, the OBDView Diagnostic Display is classified as Safety Class A. The Vehicle Diagnostic Display App is a purely informational system for Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use with no control over therapeutic delivery, diagnostic decision-making, or life-sustaining functions. Software failure would result in loss of informational display, not patient harm.


[System] You are 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 management integration into the lifecycle for VibeCheck Vibration Analyzer, a Class A Vibration Analysis Instrument Firmware. Reference IEC 62304 Clauses 7.1, 7.1.1.
Portable vibration analysis firmware for predictive maintenance of industrial rotating machinery. FFT analysis of accelerometer data.

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


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

[User]
Write a SDP section on SOUP identification and management for AquaGuard Water Quality Monitor, a Class A Water Quality Monitoring Firmware. Reference IEC 62304 Clause 8.1.2.
Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

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


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

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

"The development plan references IEC 62304 Clause 5.7.6 and Clause Annex B.3 for the RadBeam Planner."

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


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

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

"The SleepWell test plan covers system-level tests only. Each requirement in the SRS maps to one or more system test cases. No unit or integration testing is planned for this Class A sleep quality display app. Test execution is documented per Clause 5.7.5."

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


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

[User]
Expand requirement SRS-DATA-001: "data retention period" (Category: data)
Project: CardioCloud ECG Analysis Service | Cloud ECG Analysis SaMD | Class B
Automated arrhythmia detection and ECG interpretation as a cloud service for remote clinics. Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

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

[Assistant]
Description: The CardioCloud ECG Analysis Service shall retain measurement data in non-volatile storage for the specified minimum retention period, after which data may be overwritten.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Cloud ECG Analysis SaMD.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

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

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

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


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

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

[Assistant] Content: Source code for the FallRisk Inpatient Assessment Tool Fall Risk Assessment App is written in TypeScript/React and compiled for Web SPA. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


[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 BloodBank Manager (blood bank inventory system, Class A):

"Each BloodBank Manager unit undergoes boundary value analysis, equivalence class partitioning, and error guessing as part of unit verification per Clause 5.5."

[Assistant]
Verdict: FAIL
Note: Content mandates unit verification techniques per Clause 5.5 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 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):

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

[Assistant]
Verdict: FAIL
Note: The documentation references "IEC 62304-5" which is incorrect. IEC 62304 has no Part 5. 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 LabView Portal (read-only lab results viewer, Class A):

"Software unit acceptance criteria for the LabView Portal include boundary value testing, equivalence partitioning, and error guessing per Clause 5.5.3."

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


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

[User]
Write a SDP section on cybersecurity and health IT standards for VitalPulse SpO2 Monitor, a Class B Pulse Oximeter Firmware. Reference IEC 62304 Clause 5.1.2.
Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

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


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

[User]
Expand requirement SRS-DATA-002: "measurement record integrity" (Category: data)
Project: HumidityMap Room Condition Logger | Environmental Condition Logger | Class A
Monitoring and logging temperature/humidity in hospital storage areas. Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

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 HumidityMap Room Condition Logger shall detect corrupted measurement records through integrity checking and flag affected entries for review.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Environmental Condition Logger are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Intentionally corrupted records are detected and flagged with 100% detection rate across 100 injected corruption events.
Source: System requirement


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

[User]
Write a SRS section on data processing and transformation requirements for TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clause 5.2.2.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

[Assistant] Content: The TeleRehab Remote Patient Monitor data pipeline requirements specify end-to-end data flow from IMU wearable through processing to output on WebRTC. Requirements include input validation, range checking, unit conversion, and output formatting for Remote physiotherapy monitoring with exercise tracking and therapist-patient video sessions.


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

[User]
Write a SRS section on requirements conventions and identification scheme for ClinTrial EDC Platform, a Class A Clinical Trial EDC Web Platform. Reference IEC 62304 Clauses 5.2.1, 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: Requirements in this SRS are identified using the format SRS-CLI-NNN, where NNN is a sequential number. Each requirement states a single testable capability per Clause 5.2.2 and is classified as functional, performance, interface, or safety. Derived requirements that do not trace to a system requirement are flagged for separate review.


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

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

[Assistant] Content: Cybersecurity requirements for the WaterPure Quality Logger follow IEC 81001-5-1:2021 for health software and health IT systems security, addressing the full product lifecycle of the Water Quality Data Logger from design through decommissioning. Where the software is classified as health software running on general-purpose platforms, IEC 82304-1:2016 applies to the overall product safety.


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

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

"The PhysioTrack Rehab development follows IEC 14971 for the software lifecycle."

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

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

"Integration testing validates the interaction between all RadView DICOM software components."

[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-INTF-001: "sensor data link requirements" (Category: interface)
Project: TriagePro Emergency Scoring App | Emergency Department Triage SaMD | Class B
Guiding emergency department triage scoring using the Manchester Triage System protocol. Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

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 Emergency Department Triage SaMD sensor interface shall establish and maintain reliable communication with the primary sensor via HL7 FHIR to hospital EMR.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Emergency Department Triage SaMD output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

[User]
Write a SRS section on data retention and integrity requirements for 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: Data requirements for the TrainCert Staff Certification Tracker specify retention periods, storage formats, and integrity controls for all persistent data managed by the Training Certification System. Data integrity is ensured through checksums or cryptographic hashes, and corrupted data is detected before use in any processing function.


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

"Problem resolution follows established procedures and best practices. Issues are tracked and resolved in a timely manner as appropriate."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "best practices", "established procedures" 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 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 WeightAlert Neonatal Scale, a Class B Neonatal Scale Firmware. Reference IEC 62304 Clause 5.3.1.
Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

[Assistant] Content: The WeightAlert Neonatal Scale Software Architecture Document establishes the high-level design structure of the Neonatal Scale Firmware per Clause 5.3.1. It defines the decomposition into software items, their interfaces, and the rationale for design decisions including technology choices and architectural patterns on MSP430.


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

"Compliance with IEC 62304 Clause Annex A.1 (post-market surveillance) and Clause 11.1 (performance benchmarking) is demonstrated."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses Annex A.1 and 11.1, neither of which exists. IEC 62304 annexes are informative, not cited as requirements. IEC 62304 has no Clause 11. All clause references must be corrected.


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

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

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

[Assistant]
Description: A deterministic safe-state transition shall be triggered by any detected critical fault condition in the BrachyDose HDR Afterloader Controller, with all active outputs brought to a known safe configuration.
Rationale: Fail-safe behavior is essential to prevent the HDR Brachytherapy Afterloader 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 primary international standards applicable to development for GasMonitor Anesthetic Gas Logger, a Class A Anesthetic Gas Concentration Logger. Reference IEC 62304 Clause 5.1.2.
Software logging waste anesthetic gas concentrations in operating rooms for occupational safety compliance. Recording only.

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


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

[User]
Write a SDP section on tool qualification for Class B and C for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clause 5.1.4.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

[Assistant] Content: Tool qualification for the DoseVerify In-Vivo Dosimetry System is performed for all tools whose output directly supports verification conclusions, per Clause 5.1.4. Qualified tools include the C++ / Python build toolchain, code coverage analyzers, and the system test harness. Each tool's qualification record is maintained as a controlled document.


[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 safety requirements for Class A -- confirms no safety functions for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: As a Class A system, the InhaleSense Smart Inhaler Tracker does not implement software safety functions. The Smart Inhaler Adherence Tracker presents MEMS pressure sensor for informational purposes only. No risk control measure per Clause 5.2.3 is implemented in software -- all identified risks are addressed by the informational-only design.


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

[Assistant] Content: The SunGuard UV Index Display is developed in C (embedded) targeting the STM32L4 platform. Source code is maintained under version control with branching and tagging conventions defined in SOP-012. Build automation ensures reproducible compilation, and all toolchain versions are recorded as part of the configuration management baseline.


[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 AssetTrack Equipment Inventory, a Class A Equipment Inventory System. Reference IEC 62304 Clauses 5.7, 5.7.4.
Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

[Assistant] Content: The AssetTrack Equipment Inventory system test suite runs on Android 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 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):

"This plan is prepared in compliance with IEC 62304:2015 and ISO 13485:2016."

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


[System] You are 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 RenalDose Renal Adjustment Calculator, a Class B Renal Dose Adjustment Calculator. Reference IEC 62304 Clause 5.2.2.
Calculator adjusting medication doses for patients with impaired renal function based on eGFR.

[Assistant] Content: The RenalDose Renal Adjustment Calculator shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Renal Dose Adjustment Calculator must sustain from input sources without data loss or processing backlog on Web SPA.


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

[User]
Write a SDP section on risk control verification and traceability for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: Risk control measures in the TransVent Transport Ventilator are verified per Clause 7.3.1 through the testing activities appropriate to the safety classification. Traceability per Clause 7.3.2 links each identified hazard to its risk control measure, the software requirement implementing the control, and the test case verifying the control's effectiveness in the Transport Ventilator Firmware.


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

[User]
Write a FMEA section on FMEA scope for Class A -- simplified analysis for PowerTrack UPS Monitor, a Class A UPS Monitoring Software. Reference IEC 62304 Clause 7.1.1.
Software monitoring uninterruptible power supply status for critical medical equipment rooms. Logs voltage, load, and battery health.

[Assistant] Content: This simplified FMEA for the PowerTrack UPS Monitor UPS Monitoring Software addresses Clause 7.1.1 by identifying software items that could contribute to hazardous situations. The analysis concludes that the Class A system has no failure modes leading to patient harm -- all failure effects are limited to degraded or absent informational display.


[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 fault tree analysis identifies root causes of potential software failures. Control measures include watchdog timers, redundant calculations, and plausibility checks on sensor data. Each measure is a traceable software requirement verified during system testing."

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


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

[User]
Write a SDP section on primary international standards applicable to development for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clause 5.1.2.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

[Assistant] Content: The PressoTrack Blood Pressure Trending development lifecycle is governed by IEC 62304:2006+AMD1:2015. Risk management follows ISO 14971:2019. The quality management system underpinning all activities conforms to ISO 13485:2016. Usability engineering for the Ambulatory Blood Pressure Monitor Firmware interface adheres to IEC 62366-1:2015+AMD1:2020.


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

[User]
Write a SDP section on change control process for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clauses 8.2, 8.2.1.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

[Assistant] Content: Changes to the TempWatch Body Temperature Logger software baseline require a documented change request approved before implementation. The change control process per Clause 8.2 includes impact assessment on safety, regression risk evaluation, and verification of the change before integration into the controlled baseline.


[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 FridgeGuard Temperature Logger, a Class A Cold Chain Temperature Logger. Reference IEC 62304 Clause 5.2.2.
Firmware logging refrigerator temperatures for vaccine and medication cold chain compliance. Records and displays data, no alerts that drive clinical decisions.

[Assistant] Content: Operational context: the FridgeGuard Temperature Logger is a Cold Chain Temperature Logger used for Continuous logging and display of storage temperatures for compliance documentation. The software executes on ATmega328P and interfaces with DS18B20 temperature sensor for data acquisition. The user population and use environment define the requirements for usability, reliability, and performance.


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

"REQ-SRS-012: The ArthroNav shall log all user actions with timestamps in an audit trail stored in non-volatile memory. The audit trail shall retain at least 10,000 entries. Acceptance criterion: verify log persistence across power cycles and entry count capacity. Priority: Mandatory. Source: Regulatory."

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


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

[User]
Expand requirement SRS-PERF-002: "real-time performance requirement" (Category: performance)
Project: DoseCalc Medication Calculator | Medication Dose Calculator App | Class B
Calculating weight-based medication doses for clinical prescribing support. Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

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: Processing latency of the Medication Dose Calculator App shall be bounded to ensure timely output that reflects current input conditions.
Rationale: Bounded processing latency ensures the Medication Dose Calculator App provides readings reflecting the current state without clinically significant delay.
Priority: Mandatory
Acceptance Criterion: End-to-end latency is within the specified limit for 99.9% of samples over a 24-hour test period.
Source: System requirement


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

[User]
Write a SRS section on system boundaries and external dependencies for HomeVent BiPAP Controller, a Class C BiPAP Device Firmware. Reference IEC 62304 Clause 5.2.2.
Home bilevel positive airway pressure device firmware. Manages inspiratory/expiratory pressure, leak compensation, and patient triggering.

[Assistant] Content: The HomeVent BiPAP Controller software boundary encompasses the BiPAP Device Firmware application executing on ARM Cortex-M7. External dependencies include flow sensor hardware and BLE. 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. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-FUNC-004: "device configuration management" (Category: functional)
Project: PressoTrack Blood Pressure Trending | Ambulatory Blood Pressure Monitor Firmware | Class B
Automated periodic blood pressure measurement and trending over 24 hours. Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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

[Assistant]
Description: Configuration changes to the PressoTrack Blood Pressure Trending shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the Ambulatory Blood Pressure Monitor Firmware to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

[User]
Write a SRS section on purpose of the SRS document for PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clause 5.2.1.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

[Assistant] Content: The SRS for the PainScale Digital Assessment Tool documents every functional, performance, interface, and safety requirement governing the Pain Assessment Tool. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


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

[User]
Expand requirement SRS-FUNC-005: "power-on self-test sequence" (Category: functional)
Project: StrokeAlert CT Perfusion Analyzer | AI Stroke Triage CT Perfusion SaMD | Class C
Rapid automated CT perfusion analysis generating ischemic core and penumbra maps for acute stroke treatment decisions. Time-critical cloud SaMD processing CT perfusion scans to generate ischemic core and penumbra maps for acute stroke triage. Results pushed to mobile app within 5 minutes.

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

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


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

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

"The MedInventory addresses IEC 62304 Clause 11.1 (deployment validation) through formal review."

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


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

[User]
Write a SRS section on user interaction requirements for PulmoCheck Spirometry Analyzer, a Class B Spirometry Analysis Software. Reference IEC 62304 Clause 5.2.2.
Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

[Assistant] Content: The PulmoCheck Spirometry Analyzer user interaction requirements define the observable behavior of the Spirometry Analysis Software from the user's perspective. Requirements are organized by use scenario and specify the information displayed, the timing of updates, and the user actions supported during Analysis and interpretation of spirometry test data with predicted value comparison.


[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 NurseCall Hub (patient call system dashboard, Class A):

"Software problem resolution follows ISO 14971:2020 Clause 9."

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


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

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

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

[User]
Write a SDP section on development platform and build infrastructure for PathCloud AI Histology Analyzer, a Class B Cloud SaMD Histopathology Analysis Platform. Reference IEC 62304 Clause 5.1.4.
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: Source code for the PathCloud AI Histology Analyzer Cloud SaMD Histopathology Analysis Platform is written in Python (PyTorch) + TypeScript (frontend) and compiled for AWS ECS (GPU instances) + React SPA. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


[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 TriagePro Emergency Scoring App, a Class B Emergency Department Triage SaMD. Reference IEC 62304 Clause 5.2.2.
Standalone tablet app implementing Manchester Triage System scoring. Guides clinicians through triage flowchart and records patient acuity level.

[Assistant] Content: Enhanced security requirements for the TriagePro Emergency Scoring App address the elevated risk profile of the Emergency Department Triage SaMD. Requirements include secure boot verification, integrity checking of critical data structures, tamper detection on HL7 FHIR to hospital EMR, and a defined vulnerability response process per IEC 81001-5-1:2021.


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

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

"The PillRemind software architecture per Clause 5.3 is decomposed to the unit level with detailed interface specifications for every inter-unit boundary."

[Assistant]
Verdict: FAIL
Note: Content mandates architectural decomposition per Clause 5.3 for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Architectural design (Clause 5.3) is not required for Class A.


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

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

"The MedInventory verification approach is commensurate with Class A risk. System tests validate end-to-end functionality. No formal code coverage metrics are required. The developer may self-verify test results."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. 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 requirements verification approach for DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clause 5.2.6.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: The DialyFlow Dialysis Fluid Controller requirements verification checklist per Clause 5.2.6 confirms: no ambiguous requirements, no untestable requirements, no contradictions between requirements, and complete traceability to system requirements and risk controls. The review is documented with reviewer names, findings, and disposition.


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

[User]
Expand requirement SRS-FUNC-006: "audit trail and data export" (Category: functional)
Project: PressoTrack Blood Pressure Trending | Ambulatory Blood Pressure Monitor Firmware | Class B
Automated periodic blood pressure measurement and trending over 24 hours. Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

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 Ambulatory Blood Pressure Monitor Firmware shall maintain a timestamped record of all measurements in non-volatile storage, supporting export via BLE 5.0.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


[System] You are an IEC 62304 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 architecture identifies segregation necessary for risk control per Clause 5.3.5."

[Assistant]
Verdict: FAIL
Note: Content mandates architectural design documentation for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Architectural design (Clause 5.3) is not required for Class A.