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

[Assistant] Content: The ClinTrial EDC Platform safety requirement section confirms the absence of safety-critical functions. The Clinical Trial EDC Web Platform operates as a display-only system for Electronic capture and management of clinical trial data across multiple investigator sites, with no closed-loop control, no clinical alarms, and no automated decision-making. The risk analysis confirms no software failure mode contributes to a hazardous situation.


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

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

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

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


[System] You are a 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: "device configuration management" (Category: functional)
Project: BreathEasy Air Quality Display | Environmental Air Quality Display | Class A
Informational display of indoor air quality metrics for general awareness. Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

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

[Assistant]
Description: The BreathEasy Air Quality Display shall allow authorized users to configure operating parameters via I2C and persist settings across power cycles.
Rationale: Configurable parameters allow the Environmental Air Quality Display to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

[User]
Write a SDP section on internal SOPs and procedures for WoundTrack Healing Analyzer, a Class B Wound Assessment App. Reference IEC 62304 Clause 5.1.2.
Mobile app photographing wounds and measuring area/perimeter over time to track healing progress for clinician review.

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


[System] You are a regulatory 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 OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 7.1, 7.1.1.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: The OBDView Diagnostic Display risk management process is concurrent with development, not sequential. Software causes of hazardous situations are identified per Clause 7.1 and documented per Clause 7.1.4. Risk controls are implemented as software requirements and verified through the applicable testing levels for the Vehicle Diagnostic Display App.


[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 DialyFlow Dialysis Fluid Controller, a Class C Hemodialysis Fluid Controller Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware controlling dialysate flow rates and composition in a hemodialysis machine. Fluid balance errors could be fatal.

[Assistant] Content: Persistent data managed by the DialyFlow Dialysis Fluid Controller includes configuration parameters, acquired measurements from conductivity sensors (x2), and operational logs. Data integrity requirements specify error detection mechanisms and the Hemodialysis Fluid Controller Firmware response to data corruption events.


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

[User]
Write a SDP section on purpose and scope for Class A with minimal documentation for TempWatch Body Temperature Logger, a Class A Temperature Logging Firmware. Reference IEC 62304 Clause 5.1.1.
Firmware for a wearable temperature patch that logs skin temperature over 24 hours and displays trends. No fever detection or alerts.

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


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

[User]
Write a SDP section on risk control requirements traceability for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.2.3.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: Clause 5.2.3 requires that risk control measures implemented in the AirSentry Urban Air Quality Station software appear as traceable requirements. The traceability chain runs from the ISO 14971 hazard analysis to the SRS requirement to the test case verifying the control's effectiveness in the Air Quality Monitoring Station 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 risk control measures and implementation for MindCalm Meditation Timer, a Class A Meditation Wellness App. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Mobile app providing guided meditation timers with optional heart rate display during sessions. Heart rate shown for interest only, not diagnostic.

[Assistant] Content: Risk control measures for the MindCalm Meditation Timer are defined per Clause 7.2.1 and implemented in software per Clause 7.2.2. Controls include input validation for data inputs, range checking on processed values, and timeout detection on HealthKit/Google Fit API. Each control is traced to a software requirement and verified through testing.


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

[User]
Write a SDP section on milestones and phase transition criteria for SleepScore Apnea Screening Tool, a Class B Sleep Apnea Screening App. Reference IEC 62304 Clause 5.1.1.
Mobile app analyzing overnight audio recordings to screen for obstructive sleep apnea indicators. Screening only, not diagnostic.

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


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

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

"Configuration management is established. Configuration items are identified. Configuration items are controlled. Configuration status is reported. Configuration management is performed. Configuration is managed."

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


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

[Assistant] Content: This Software Development Plan establishes the lifecycle framework for the PathSlide Digital Pathology Viewer Digital Pathology Viewer, defining all development activities, deliverables, and verification milestones in compliance with IEC 62304 Clause 5.1.1. As a Class A system that cannot contribute to a hazardous situation, the documentation scope is intentionally minimal, focusing on system-level verification and requirements traceability rather than detailed design or unit-level testing.


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

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

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


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

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

[Assistant] Content: The safety classification of the DoseVerify In-Vivo Dosimetry System was determined per IEC 62304 Clause 4.3, considering the software's contribution to hazardous situations identified in the ISO 14971 risk analysis. The classification is documented in the risk management file and reviewed whenever the intended use, system architecture, or risk profile of the In-Vivo Dosimetry Verification Software changes.


[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 hazard identification for the specific device for OBDView Diagnostic Display, a Class A Vehicle Diagnostic Display App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

[Assistant] Content: For the OBDView Diagnostic Display, potential software contributions to hazardous situations include input data corruption, processing algorithm errors, and Bluetooth OBD-II adapter communication failures. Each identified cause is evaluated for severity and probability, with risk control measures defined per Clause 7.2.1 and traced to software requirements.


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

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

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

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


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

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

"Compliance with IEC 62304 Clause 5.6.8 (performance benchmarking) and Clause Annex A.1 (security testing) is demonstrated."

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


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

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

[Assistant] Content: Requirements for the PostureGuard Desk 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 SRS section on baseline security requirements for RoomBoard Digital Signage, a Class A Patient Room Digital Signage. Reference IEC 62304 Clause 5.2.2.
Hospital room digital signage displaying patient name, care team, and daily schedule. Display-only, no clinical data entry.

[Assistant] Content: The RoomBoard Digital Signage Patient Room Digital Signage implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

[User]
Write a THREAT section on threat model data flow decomposition for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clause 5.2.2.
Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

[Assistant] Content: The DermaAssist Skin Lesion Classifier data flow diagrams for threat analysis map all data movement within and across the Skin Lesion Classification App boundary. Trust boundaries are placed at external interfaces (camera API, cloud inference API), persistent storage, and inter-process communication points.


[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 architecture verification scope for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clauses 5.3.1, 5.3.6.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

[Assistant] Content: Verification of the RadOnco Cloud Treatment Planner architecture per Clause 5.3.6 is a phase gate requirement. The review confirms completeness of requirements coverage, correctness of interface definitions, and adequate risk control implementation in the Cloud Radiation Treatment Planning SaMD design.


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

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

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

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


[System] You are 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 InsuPrecise Insulin Pump Controller, a Class C Insulin Pump Controller Firmware. Reference IEC 62304 Clause 8.1.2.
Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

[Assistant] Content: SOUP components in the InsuPrecise Insulin Pump Controller are catalogued per Clause 8.1.2 with title, version, supplier, and license terms. The risk management process evaluates each SOUP item's known anomaly list per Clause 7.1.3 to determine whether any published defect could contribute to a hazardous situation in the Insulin Pump Controller Firmware.


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

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

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


[System] You are an IEC 62304 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 HeartLink (cardiac telemetry system, Class B):

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

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


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

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

"Documentation is prepared in accordance with standard templates and guidelines. Review cycles are established at appropriate intervals for the pacemaker programmer."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "appropriate intervals" provide no project-specific information about the PacePilot pacemaker programmer. 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 SDP section on milestones and phase transition criteria for AllergyCard Patient Allergy Viewer, a Class A Patient Allergy Display. Reference IEC 62304 Clause 5.1.1.
Kiosk display showing patient allergy information from the hospital ADT system. Read-only, no modification capability.

[Assistant] Content: The AllergyCard Patient Allergy Viewer development schedule is anchored to formal milestones with documented transition criteria. Progress is measured against these gates rather than calendar dates, ensuring the Patient Allergy Display meets all quality and safety requirements before advancing to the next lifecycle phase.


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

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

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


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

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

"The lifecycle processes for the RadBeam Planner comply with ISO 14971:2020."

[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 LabView Portal (read-only lab results viewer, Class A):

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

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


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

"Code reviews for the LabView Portal shall be performed by at least two reviewers independent of the development team, following a formal checklist."

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


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

[User]
Write a FMEA section on documenting failure modes and their effects for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: Each identified failure mode of the RadView DICOM Viewer is documented per Clause 7.1.4 with the failure mode description, potential causes, local effects, end effects on the Medical Image Viewer, severity classification, and existing controls. The documentation supports risk control decision-making per Clause 7.2.1.


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

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

"Software unit acceptance criteria for the CaloriePal 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 an IEC 62304 regulatory documentation expert. Expand requirements with description, rationale, priority, acceptance criterion, and source.

[User]
Expand requirement SRS-SEC-001: "access control and authorization" (Category: security)
Project: AquaGuard Water Quality Monitor | Water Quality Monitoring Firmware | Class A
In-situ measurement of water quality parameters for environmental monitoring. Firmware for a multi-parameter water quality probe measuring pH, dissolved oxygen, conductivity, and turbidity in rivers and lakes.

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 Water Quality Monitoring Firmware shall be restricted to authenticated and authorized users.
Rationale: Unauthorized configuration changes to the Water Quality Monitoring Firmware could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Configuration modification is rejected when attempted without valid credentials, verified across all configurable parameters.
Source: Risk control


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

[User]
Write a SDP section on system test execution and acceptance for Class A for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clauses 5.7, 5.7.4.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: Acceptance of the RadView DICOM Viewer is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Medical Image Viewer.


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

[User]
Expand requirement SRS-INTF-002: "primary sensor interface protocol" (Category: interface)
Project: VitalPulse SpO2 Monitor | Pulse Oximeter Firmware | Class B
Continuous monitoring of blood oxygen saturation and pulse rate with clinical alarms. Bedside pulse oximeter firmware displaying SpO2 and pulse rate with configurable alarm thresholds. Incorrect readings could delay treatment.

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 Pulse Oximeter Firmware sensor interface shall establish and maintain reliable communication with the MAX30102 dual-wavelength PPG via I2C.
Rationale: Sensor link integrity directly impacts data quality and the reliability of the Pulse Oximeter Firmware output.
Priority: Mandatory
Acceptance Criterion: Error injection tests confirm 100% detection rate for corrupted frames and recovery within specified timeout.
Source: System requirement


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

"Independent review is required for all Class C deliverables of the VentAssist Pro. System verification is performed by personnel not directly responsible for the development of the item under review. Code reviews are conducted by qualified engineers who were not the original authors."

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


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

[User]
Expand requirement SRS-FUNC-002: "real-time data presentation on I2C" (Category: functional)
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: Output presentation on the I2C shall refresh at the configured interval, reflecting the most recent processed data from the UV Exposure Display Firmware pipeline.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


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

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

"In accordance with IEC 62304:2020, verification activities include system testing."

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


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

[User]
Write a SDP section on milestones and phase transition criteria for DermaLens Teledermatology Platform, a Class B Cloud Teledermatology SaMD. Reference IEC 62304 Clause 5.1.1.
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: Milestones governing the DermaLens Teledermatology Platform lifecycle include Requirements Baseline, Architecture Baseline, Implementation Complete, Verification Complete, and Release Readiness. Each milestone has defined entry and exit criteria documented in this plan. No milestone can be declared complete while open problem reports of severity "major" or higher remain unresolved.


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

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

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


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

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

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

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


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

[User]
Write a SRS section on purpose of the SRS document for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clause 5.2.1.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: The SRS for the NutriView Food Diary documents every functional, performance, interface, and safety requirement governing the Nutritional Tracking Display App. Requirements originate from the system specification, the ISO 14971 risk analysis, and regulatory requirements. Traceability per Clause 5.2.1 links each requirement to its source and forward to its verification activity.


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

[User]
Write a FMEA section on documenting failure modes and their effects for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clauses 7.1.2, 7.1.4.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: The NutriView Food Diary FMEA documents each failure mode per Clause 7.1.4, providing sufficient detail for risk evaluation: the software function affected, the failure mode, the cause(s), the effect on the Nutritional Tracking Display App output, and the resulting hazard severity. This documentation is maintained in the risk management file.


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

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

[Assistant] Content: Performance requirements for the VitalPulse SpO2 Monitor specify maximum latencies, throughput rates, and resource consumption limits for the Pulse Oximeter Firmware operating on ARM Cortex-M4. Latency requirements define the maximum time from input event to output response for each critical processing path during Continuous monitoring of blood oxygen saturation and pulse rate with clinical alarms.


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

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

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

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


[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 BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: The BrachyDose HDR Afterloader Controller HDR Brachytherapy Afterloader Firmware is deployed in an environment where Controlling radioactive source stepping positions and dwell times for high-dose-rate brachytherapy. Users include trained clinical staff and, where applicable, patients or caregivers. The Dual redundant PLC platform defines the computational environment, while stepper motor driver provides the primary data communication pathway.


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

[User]
Expand requirement SRS-PERF-002: "data processing timing constraint" (Category: performance)
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: End-to-end latency from VEML6075 UV sensor data acquisition to output presentation shall not exceed the specified limit under normal operating conditions.
Rationale: Real-time performance is critical for the UV Exposure Display Firmware to support timely clinical decisions based on current data.
Priority: Mandatory
Acceptance Criterion: Worst-case latency measured under maximum load conditions does not exceed the specified absolute maximum.
Source: System requirement


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

[User]
Expand requirement SRS-SAFE-001: "independent watchdog monitoring" (Category: safety)
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: An independent hardware watchdog shall monitor the StrokeAlert CT Perfusion Analyzer main processing loop, triggering a safe-state reset if the software fails to service the watchdog within the specified timeout.
Rationale: Hardware-independent monitoring ensures that a frozen main processor cannot leave the AI Stroke Triage CT Perfusion SaMD in an unsafe operating state.
Priority: Mandatory
Acceptance Criterion: Watchdog independence verified: main processor halt results in watchdog-initiated recovery within timing specification.
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 ChemoCalc (chemotherapy dose calculator, Class C):

"Post-market activities are conducted as required by applicable regulations. Feedback mechanisms are established per best practices for the ChemoCalc."

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


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

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

"The LabView Portal coding standards require Test-Driven Development. All code shall have corresponding unit tests achieving 80% branch coverage before merge."

[Assistant]
Verdict: FAIL
Note: Content mandates Test-Driven Development with 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 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a TRACE section on traceability scope including risk controls for CardioLoop Cardiac Resync Controller, a Class C CRT Optimization Firmware. Reference IEC 62304 Clauses 5.7.1, 7.3.2.
Firmware for cardiac resynchronization therapy devices optimizing biventricular pacing based on hemodynamic feedback.

[Assistant] Content: The CardioLoop Cardiac Resync Controller traceability matrix extends beyond functional requirements to include risk control traceability per Clause 7.3.2. Each risk control measure implemented in the CRT Optimization Firmware software is traced from the ISO 14971 hazard through the software requirement to the verification test confirming its effectiveness.


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

[User]
Write a SDP section on verification strategy for Class C -- unit, integration, and system with coverage for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clauses 5.5, 5.5.2, 5.6, 5.7.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

[Assistant] Content: Class C verification of the CochleaMap CI Fitting Software requires unit testing with statement coverage of at least 90%, branch coverage of at least 80%, and MC/DC coverage of at least 80% for safety-critical modules. Integration testing per Clause 5.6 verifies all inter-unit interfaces including USB programming cable, desktop GUI. System-level verification per Clause 5.7 is performed by independent personnel not directly responsible for development.


[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 FactoryTemp Industrial Temperature Monitor, a Class A Industrial Temperature Monitoring Firmware. Reference IEC 62304 Clauses 5.7, 5.7.4.
Firmware monitoring factory floor temperatures from distributed thermocouple arrays. Logs data for process control compliance.

[Assistant] Content: Acceptance of the FactoryTemp Industrial Temperature Monitor is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Industrial Temperature Monitoring 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 SRS section on user interaction requirements for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 5.2.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: The GrowthChart Pediatric Viewer Growth Chart Display App presents information to the user via FHIR Observation API and accepts user input through defined interaction patterns. User interaction requirements are traceable to the usability engineering file per IEC 62366-1:2015+AMD1:2020.


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

[User]
Write a SDP section on tool qualification for Class B and C for InsuPrecise Insulin Pump Controller, a Class C Insulin Pump Controller Firmware. Reference IEC 62304 Clause 5.1.4.
Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

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


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

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

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

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


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

[User]
Write a SAD section on architectural overview for Class C with segregation for ChemoFlow Infusion Controller, a Class C Chemotherapy Infusion Pump Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.2, 5.3.5.
Firmware for a chemotherapy infusion pump controlling precise drug delivery rates. Dosing errors could be life-threatening.

[Assistant] Content: The ChemoFlow Infusion Controller Chemotherapy Infusion Pump Firmware architecture implements segregation per Clause 5.3.5 to isolate safety-critical software items from non-safety items. The safety-critical path -- from drop counting sensor acquisition through processing to safety output -- is architecturally independent from auxiliary functions. This segregation supports the Class C verification strategy including independent review.


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

"REQ-SRS-078: The ThermoGuard shall maintain data integrity during concurrent access by multiple users. No data corruption or loss shall occur. Acceptance criterion: execute concurrent read/write operations and verify data consistency. Priority: Mandatory. Source: System requirement."

[Assistant]
Verdict: PASS
Note: Content requirement is properly structured with measurable acceptance criteria. 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 THREAT section on system description for threat modeling for HandGrip Strength Dynamometer, a Class B Hand Dynamometer Firmware. Reference IEC 62304 Clause 5.2.1.
Digital hand dynamometer firmware measuring grip strength and fatigue over repeated trials for rehabilitation assessment.

[Assistant] Content: The HandGrip Strength Dynamometer threat model system description per IEC 81001-5-1:2021 identifies the Hand Dynamometer Firmware as the subject, with trust boundaries at each external interface. Assets include software integrity, data confidentiality, and service availability during Measuring hand grip strength and fatigue patterns for rehabilitation progress tracking.


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

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

"The OxyPure Controller SOUP risk evaluation examines published anomaly lists per Clause 7.1.3. Known anomalies in third-party libraries are assessed for potential contribution to hazardous situations. Mitigations include version pinning, input validation, and fallback behavior when SOUP components fail."

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


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

[User]
Write a SDP section on problem reporting and investigation for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clauses 9.1, 9.2.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

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


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

[User]
Write a SAD section on architectural overview for Class B for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: Architectural design of the BalanceBoard Vestibular Trainer uses a modular decomposition that separates input handling, business logic, and output generation. Each module has a defined interface per Clause 5.3.2. The Balance Training Platform Firmware architecture on STM32H7 + display facilitates integration testing at module boundaries.


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

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

[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 requirements engineer for IEC 62304 medical device software. Expand requirements into structured fields with specific, measurable descriptions. Priority must be Mandatory, Desirable, or Optional. Acceptance criteria must be testable. Do not fabricate standard references. IEC 62304 is a single-part standard with no sub-parts.

[User]
Expand requirement SRS-FUNC-001: "continuous data sampling from MOSFET dosimeters" (Category: functional)
Project: DoseVerify In-Vivo Dosimetry System | In-Vivo Dosimetry Verification Software | Class C
Real-time verification of delivered radiation dose using in-vivo dosimeter measurements during treatment. Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

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

[Assistant]
Description: The DoseVerify In-Vivo Dosimetry System software shall acquire MOSFET dosimeters data at the specified sampling rate and store values in a circular buffer for processing by the In-Vivo Dosimetry Verification Software signal pipeline.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the In-Vivo Dosimetry Verification Software.
Priority: Mandatory
Acceptance Criterion: System test confirms zero missed samples over a 24-hour continuous operation period at the maximum configured sampling rate.
Source: System requirement


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

[User]
Review this documentation excerpt for the ArthroNav (surgical navigation system, Class C):

"Post-market activities are conducted as required by applicable regulations. Feedback mechanisms are established per best practices for the ArthroNav."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "best practices", "as required by" provide no project-specific information about the ArthroNav surgical navigation 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 SDP section on internal SOPs and procedures for IncidentReport Clinical Event Logger, a Class A Incident Reporting System. Reference IEC 62304 Clause 5.1.2.
Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

[Assistant] Content: Work instructions for the IncidentReport Clinical Event Logger are codified in SOPs maintained within the ISO 13485 quality management system. SOP-010 (development planning), SOP-011 (risk management), SOP-012 (configuration management), and SOP-013 (verification) define step-by-step procedures for each IEC 62304 lifecycle activity applicable to the Incident Reporting System.


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

[User]
Write a SDP section on problem reporting and investigation for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clauses 9.1, 9.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: The problem resolution process for the CardioCloud ECG Analysis Service follows Clauses 9.1 through 9.8. Each problem report is classified by severity, investigated for root cause, and resolved through the change control process. Records are maintained per Clause 9.5, and all resolutions are verified per Clause 9.7 before the Cloud ECG Analysis SaMD baseline is updated.


[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: "device configuration management" (Category: functional)
Project: LinacControl Beam Delivery System | Linear Accelerator Control Software | Class C
Controlling radiation beam delivery including gantry position, collimator settings, and dose monitoring. Software controlling linear accelerator beam delivery during radiation therapy. Beam-on errors could deliver lethal radiation doses.

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 LinacControl Beam Delivery System shall allow authorized users to configure operating parameters via real-time fieldbus and persist settings across power cycles.
Rationale: Parameter flexibility is essential for the Linear Accelerator Control Software 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 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 GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clauses 5.7, 5.7.4.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: Acceptance of the GrowthChart Pediatric Viewer is based solely on system test results per Clause 5.7. The test report documents pass/fail status for every requirement-derived test case, any anomalies discovered, and their disposition. Verification completeness per Clause 5.7.4 is demonstrated by the traceability matrix showing full requirements coverage. No unit or integration test results are required for this Class A Growth Chart Display App.


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

[User]
Write a SAD section on purpose of the architecture document for BeamPlan Radiation Treatment Planner, a Class C Radiation Treatment Planning Software. Reference IEC 62304 Clause 5.3.1.
Desktop software calculating radiation treatment plans including beam angles, dose distribution, and organ-at-risk constraints.

[Assistant] Content: The BeamPlan Radiation Treatment Planner Software Architecture Document establishes the high-level design structure of the Radiation Treatment Planning Software 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 Linux workstation with GPU.


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

[User]
Expand requirement SRS-SEC-001: "access control and authorization" (Category: security)
Project: AirSentry Urban Air Quality Station | Air Quality Monitoring Station Firmware | Class A
Continuous measurement and public reporting of urban air quality parameters. IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public 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 AirSentry Urban Air Quality Station shall require authentication before allowing modification of device configuration parameters via 4G LTE.
Rationale: Access control prevents unauthorized modification of the Air Quality Monitoring Station Firmware operating parameters.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


[System] You are 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 OxyPure Controller (oxygen concentrator controller, Class C):

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

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


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

[User]
Expand requirement SRS-FUNC-005: "device configuration management" (Category: functional)
Project: WeightAlert Neonatal Scale | Neonatal Scale Firmware | Class B
Precision weight measurement for neonatal patients with change-rate alerting. Neonatal scale firmware with high-precision weight measurement. Sudden weight changes may indicate fluid imbalance in NICU patients.

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 WeightAlert Neonatal Scale shall allow authorized users to configure operating parameters via SPI and persist settings across power cycles.
Rationale: Parameter flexibility is essential for the Neonatal Scale 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 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):

"Integration testing for the WoundTrack covers all interfaces between software items per Clause 5.6.1 through 5.6.7. Test content addresses data flow, timing, and error handling at each interface. Regression testing is conducted per Clause 5.6.6 after each integration step."

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

"Risk management is performed. Risk analysis is conducted. Risk evaluation is completed. Risk control measures are implemented. Risk management activities are documented. The risk management process is followed."

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


[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: "camera barcode scanner data capture and buffering" (Category: functional)
Project: AssetTrack Equipment Inventory | Equipment Inventory System | Class A
Tracking location and status of medical equipment for inventory management. Mobile app for scanning and tracking medical equipment locations via barcode. Inventory management only.

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

[Assistant]
Description: Data from the camera barcode scanner shall be acquired by the AssetTrack Equipment Inventory at the configured rate, with each sample timestamped and queued for processing.
Rationale: Reliable sensor data capture underpins all downstream processing and clinical output of the Equipment Inventory System.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

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

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

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


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

[User]
Expand requirement SRS-INTF-003: "data export and interoperability" (Category: interface)
Project: RoomBoard Digital Signage | Patient Room Digital Signage | Class A
Displaying non-clinical patient information on bedside screens. Hospital room digital signage displaying patient name, care team, and daily schedule. Display-only, no clinical data entry.

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 RoomBoard Digital Signage shall exchange data with external systems via MQTT using the specified message format with error handling.
Rationale: Interoperability enables integration of Patient Room Digital Signage data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Successful bidirectional data exchange confirmed with 1000 test messages and zero message loss.
Source: User need


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

[User]
Expand requirement SRS-FUNC-003: "device configuration management" (Category: functional)
Project: PulmoCheck Spirometry Analyzer | Spirometry Analysis Software | Class B
Analysis and interpretation of spirometry test data with predicted value comparison. Software analyzing spirometry data to calculate FEV1, FVC, and FEV1/FVC ratio with predicted value comparisons.

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 PulmoCheck Spirometry Analyzer shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the Spirometry Analysis Software 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 a regulatory compliance reviewer for IEC 62304 medical device software documentation. Review sections for completeness, accuracy, and safety-class appropriateness. Check for hallucinated standard references — IEC 62304 is a single-part standard with no sub-parts (no IEC 62304-1, -2, etc.). ISO 14971 is also single-part. Verify all cited clause numbers exist. IEC 62304 has Clauses 4 through 9 only. Output a verdict (PASS or FAIL) and a concise note.

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

"REQ-SRS-034: The DermaScan AI shall complete self-test diagnostics within 5 seconds of power-on and report any detected hardware faults. Acceptance criterion: inject simulated hardware faults and verify detection within the time limit. Priority: Mandatory. Source: System requirement."

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


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

[User]
Write a SAD section on error propagation and data integrity in the pipeline for SurgiPlan 3D Surgical Planner, a Class B 3D Surgical Planning SaMD. Reference IEC 62304 Clause 5.3.2.
Desktop SaMD for orthopedic surgeons to plan joint replacement procedures on 3D CT reconstructions. Outputs implant sizing and positioning specifications.

[Assistant] Content: Data integrity in the SurgiPlan 3D Surgical Planner pipeline is maintained through validation at every software item boundary. The architecture specifies error codes, timeout behavior, and recovery actions for each interface. The 3D Surgical Planning SaMD logs all data integrity failures for post-deployment analysis.


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

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the NeuroStim Programmer (neurostimulator programmer, Class C). 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 software development plan addresses Clause 5.1 requirements. Planning includes risk management (Clause 5.1.7), documentation (Clause 5.1.8), and configuration management (Clause 5.1.9). The plan is kept updated per Clause 5.1.2."

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


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

[User]
Write a SDP section on hazard identification for the specific device for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

[Assistant] Content: Hazard identification for the DermaAssist Skin Lesion Classifier per Clause 7.1.2 considers all software functions that could contribute to patient harm. Identified causes include incorrect smartphone camera processing, loss of communication on camera API, and failure to detect out-of-range conditions during AI-assisted classification of skin lesion images as benign or suspicious for dermatologist review.


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

"Maintenance activities follow ISO 62304 Clause 6."

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


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

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

"The ThermoGuard system testing addresses functional requirements, performance limits, and boundary conditions. As Class A software, no additional verification levels are mandated. Test anomalies are managed per the problem resolution process."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. 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 PillRemind (medication reminder app, Class A):

"The PillRemind architecture is defined. The PillRemind architecture is documented. The PillRemind architecture is verified. The PillRemind architecture is reviewed. The PillRemind architecture is approved."

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


[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 verification approach for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.2.6.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: The PaceSet Pacemaker Programmer 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 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 data paths and processing pipeline for CardioLoop Cardiac Resync Controller, a Class C CRT Optimization Firmware. Reference IEC 62304 Clauses 5.3.1, 5.3.2.
Firmware for cardiac resynchronization therapy devices optimizing biventricular pacing based on hemodynamic feedback.

[Assistant] Content: Data flows through the CardioLoop Cardiac Resync Controller in a defined pipeline: intracardiac impedance data is acquired, validated, processed through the algorithm chain, and presented via RF telemetry. Each data transformation step has defined input and output formats per Clause 5.3.2, forming the basis for integration test cases.


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

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

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

[User]
Write a SDP section on hazard identification for the specific device for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Firmware for a smart inhaler attachment detecting actuation events, tracking medication adherence, and syncing data to a mobile app and clinician portal.

[Assistant] Content: Hazard identification for the InhaleSense Smart Inhaler Tracker per Clause 7.1.2 considers all software functions that could contribute to patient harm. Identified causes include incorrect MEMS pressure sensor processing, loss of communication on BLE 5.0, and failure to detect out-of-range conditions during Detecting inhaler actuation events and tracking medication adherence for asthma management.


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

[User]
Write a SDP section on risk control requirements traceability for WaveReview EEG Archive Viewer, a Class A EEG Archive Viewer. Reference IEC 62304 Clause 5.2.3.
Desktop application for reviewing archived EEG recordings. Playback and waveform display only, no seizure detection.

[Assistant] Content: Clause 5.2.3 requires that risk control measures implemented in the WaveReview EEG Archive Viewer software appear as traceable requirements. The traceability chain runs from the ISO 14971 hazard analysis to the SRS requirement to the test case verifying the control's effectiveness in the EEG Archive Viewer.


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

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

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


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

"The SleepWell 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.