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

"Detailed design documentation per Clause 5.4 is produced for every software unit of the PillRemind."

[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 risk control verification and traceability for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

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


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

[User] Enumerate the requirements in IEC 62304 Clause 5.4.

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

- Clause 5.4: Software detailed design
- Clause 5.4.1: Subdivide software into software units
- Clause 5.4.2: Develop detailed design for each software unit
- Clause 5.4.3: Develop detailed design for interfaces
- Clause 5.4.4: Verify detailed design

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


[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: "measurement data archival" (Category: functional)
Project: RemotICU Continuous Monitoring Hub | Edge-to-Cloud ICU Monitoring Gateway | Class B
Aggregating bedside monitor data at the edge and streaming to cloud for tele-ICU clinical oversight. Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

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 RemotICU Continuous Monitoring Hub shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via HL7v2 ADT/ORU.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Logged data is retrievable after power cycle, with all timestamps accurate to within 1 second of the reference clock.
Source: User need


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

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

"Software changes to the MedInventory are evaluated for risk impact per Clause 7.4. Each change request includes a risk assessment determining whether new hazards are introduced or existing risk controls are affected. Re-verification of affected risk controls is required before release."

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for DoseVerify In-Vivo Dosimetry System, a Class C In-Vivo Dosimetry Verification Software. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Software calculating real-time delivered dose from in-vivo dosimeter readings during radiation therapy. Dose verification for patient safety.

[Assistant] Content: Each requirement for the DoseVerify In-Vivo Dosimetry System is assigned a unique identifier and tagged with its type (functional, performance, interface, or safety) per Clause 5.2.2. Requirements are written in "shall" statements that are individually testable. The requirement set is baselined and controlled under the change management process.


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

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

"Verification activities follow IEC 62304 Clause 5.1.12 for security testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.1.12 which does not exist. Clause 5.1 has 5.1.1 through 5.1.11 only. The reference must be corrected to a valid clause number.


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

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

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

[Assistant]
Description: The HydroRemind Hydration Tracker memory footprint on nRF52840 shall remain within specified limits under worst-case operational scenarios.
Rationale: Exceeding memory limits could cause undefined behavior in the Hydration Tracking Firmware, potentially affecting safety.
Priority: Mandatory
Acceptance Criterion: Peak RAM usage during worst-case scenario does not exceed the specified limit, with minimum margin remaining.
Source: System requirement


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

[User]
Write a SDP section on hazard identification for the specific device for GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clauses 7.1.2, 7.2.1.
Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose alerts.

[Assistant] Content: The GlucoSpot Continuous Glucose Display risk analysis per Clause 7.1.2 identifies software causes of hazardous situations specific to the CGM Display App: data path corruption, timing violations, resource exhaustion, and incorrect state transitions. Each cause is linked to a risk control measure per Clause 7.2.1 and implemented as a verifiable software 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 ThermoGuard (body temperature logger, Class A):

"Every software item of the ThermoGuard shall have a detailed design document reviewed by a qualified reviewer before implementation begins."

[Assistant]
Verdict: FAIL
Note: Content mandates detailed design with review 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 software.


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

[User]
Write a SDP section on development methodology for Class C with full V-model for RadOnco Cloud Treatment Planner, a Class C Cloud Radiation Treatment Planning SaMD. Reference IEC 62304 Clause 5.1.1.
Cloud-based radiation oncology treatment planning system using GPU clusters for Monte Carlo dose calculation. Treatment plans directly drive linear accelerator delivery.

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


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

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

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

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


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

[User]
Write a FMEA section on risk control measures and implementation for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: Risk control measures for the MedRef Clinical Reference App 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 REST API for DB sync. 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 SRS section on system boundaries and external dependencies for BSACalc Body Surface Area Tool, a Class B BSA Calculator Web App. Reference IEC 62304 Clause 5.2.2.
Web calculator for body surface area using Mosteller and DuBois formulas. Used for chemotherapy dose calculations.

[Assistant] Content: External dependencies of the BSACalc Body Surface Area Tool include the Web SPA operating environment, input hardware, and web form. The BSA Calculator Web App requirements assume these dependencies operate within their specified parameters; failure modes of external components are addressed in the risk analysis.


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

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


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

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

"Maintenance activities follow ISO 14971:2020 Clause 6."

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

[User]
Expand requirement SRS-INTF-002: "external system data exchange" (Category: interface)
Project: PhysioTrack Rehabilitation Monitor | Physical Therapy Tracking System | Class B
Tracking exercise performance and range of motion during physical therapy for therapist review. Wearable system tracking range-of-motion and exercise repetitions during physical therapy sessions. Generates progress reports for therapists.

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 PhysioTrack Rehabilitation Monitor shall exchange data with external systems via BLE 5.0 using the specified message format with error handling.
Rationale: Interoperability enables integration of Physical Therapy Tracking System 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 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):

"System test procedures for the NurseCall Hub are derived from the software requirements specification. Each test has defined preconditions, steps, and expected results. This is the only verification level required for Class A software."

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

"The development plan references IEC 62304 Clause 5.3.7 and Clause 5.10 for the OxyPure Controller."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clauses 5.3.7 and 5.10, neither of which exists. Clause 5.3 has 5.3.1 through 5.3.6 only. Clause 5 ends at 5.8. 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 SRS section on user interaction requirements for AirSentry Urban Air Quality Station, a Class A Air Quality Monitoring Station Firmware. Reference IEC 62304 Clause 5.2.2.
IoT firmware for urban air quality monitoring stations measuring PM2.5, NO2, O3, and CO. Publishes data to public API.

[Assistant] Content: The AirSentry Urban Air Quality Station Air Quality Monitoring Station Firmware presents information to the user via 4G LTE 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 requirements verification approach for GaitSense Walking Analysis, a Class B Gait Analysis Insole Firmware. Reference IEC 62304 Clause 5.2.6.
Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

[Assistant] Content: Verification of GaitSense Walking Analysis software requirements follows Clause 5.2.6. Reviewers confirm that every requirement is complete, consistent, testable, and traceable. Requirements that implement risk controls are additionally verified against the ISO 14971 risk management file for the Gait Analysis Insole 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 failure mode identification approach for AuditTrail QMS Event Logger, a Class A QMS Audit Trail Service. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Microservice capturing and storing quality management system audit events. Logging and reporting only.

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


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

[User]
Expand requirement SRS-INTF-002: "clinical system integration interface" (Category: interface)
Project: AutoPancreas Closed-Loop Glucose Controller | Artificial Pancreas Controller Firmware | Class C
Automated closed-loop insulin delivery based on continuous glucose monitoring with predictive algorithms. Artificial pancreas firmware integrating CGM readings with insulin pump delivery using a PID control algorithm. Life-sustaining closed-loop system.

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 AutoPancreas Closed-Loop Glucose Controller shall exchange data with external systems via BLE to CGM using the specified message format with error handling.
Rationale: Interoperability enables integration of Artificial Pancreas Controller Firmware data into the clinical workflow and patient record.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need


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

[User]
Write a FMEA section on risk control measures and implementation for HydroRemind Hydration Tracker, a Class A Hydration Tracking Firmware. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Smart water bottle firmware tracking daily water intake via a flow sensor. Displays consumption on an e-ink screen. No health recommendations.

[Assistant] Content: Risk control measures for the HydroRemind Hydration Tracker Hydration Tracking Firmware are prioritized per Clause 7.2.1: inherently safe design first, then protective measures in software, then information for safety. Software-implemented controls per Clause 7.2.2 are expressed as verifiable requirements and traced to their originating hazard.


[System] You are 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 software development conforms to IEC 62304:2015, with risk management per ISO 14971:2019."

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


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

[User]
Write a SDP section on system test execution and acceptance for Class A for NutriView Food Diary, a Class A Nutritional Tracking Display App. Reference IEC 62304 Clauses 5.7, 5.7.4.
Mobile app for manual food logging with nutritional summary display. No dietary recommendations or medical nutrition therapy.

[Assistant] Content: The NutriView Food Diary system test suite runs on iOS/Android exercising all functional, performance, and interface requirements. Clause 5.7.4 verification confirms every SRS requirement has at least one passing system test. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are outside the scope of Class A verification and are not executed.


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

[User]
Write a SRS section on data format and interoperability requirements for SupplyChain Procurement Portal, a Class A Supply Chain Procurement System. Reference IEC 62304 Clause 5.2.2.
Web portal for ordering medical supplies with approval workflows. Procurement and logistics only.

[Assistant] Content: The SupplyChain Procurement Portal data format requirements ensure interoperability with external systems connected via REST API, ERP integration. Data structures, encoding schemes, and byte ordering are fully specified. The Supply Chain Procurement System handles version mismatches in data formats gracefully.


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

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

"Risk control measures are implemented per IEC 62304:2022 Clause 7."

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


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

[User]
Write a SAD section on error propagation and data integrity in the pipeline for CogniTest Cognitive Assessment App, a Class B Cognitive Assessment Application. Reference IEC 62304 Clause 5.3.2.
Tablet app administering standardized cognitive screening tests and scoring results. Used by neuropsychologists in clinical settings.

[Assistant] Content: Error handling in the CogniTest Cognitive Assessment App Cognitive Assessment Application architecture follows a defense-in-depth principle: each software item validates its inputs independently, even if the upstream item has performed validation. Error propagation is controlled through defined error interfaces per Clause 5.3.2, preventing corruption from spreading across module boundaries.


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

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

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

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


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

[User]
Write a SDP section on risk management integration into the lifecycle for InhaleSense Smart Inhaler Tracker, a Class A Smart Inhaler Adherence Tracker. Reference IEC 62304 Clauses 7.1, 7.1.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: Integration of risk management into the InhaleSense Smart Inhaler Tracker lifecycle ensures that newly identified hazards during development trigger requirement updates, design changes, and additional verification. The risk management file is a living document updated at each phase gate, with traceability maintained per Clause 7.3.2.


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

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

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

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

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


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

[User]
Write a SRS section on system boundaries and external dependencies for ECGInsight Rhythm Interpreter, a Class B ECG Interpretation Service. Reference IEC 62304 Clause 5.2.2.
Cloud service analyzing 12-lead ECG recordings and generating preliminary rhythm interpretations for physician review.

[Assistant] Content: The ECGInsight Rhythm Interpreter software boundary encompasses the ECG Interpretation Service application executing on Cloud (GCP with GPU). External dependencies include external data sources hardware and REST API. These external systems are treated as black boxes at the software boundary, with interface requirements specified in this SRS.


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

[User]
Write a SAD section on error propagation and data integrity in the pipeline for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clause 5.3.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 architecture defines error propagation rules at each interface per Clause 5.3.2. Invalid data from smartphone camera is detected at the acquisition boundary and does not propagate into processing stages. Each software item validates its inputs and reports errors through a defined error channel in the Skin Lesion Classification App.


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

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

[Assistant] Content: Elicitation of requirements for the DermaLens Teledermatology Platform follows Clause 5.2.1, drawing on system requirements, stakeholder interviews, and the risk management file. Requirements are documented with unique identifiers and classified by type: functional, performance, interface, or safety for the Cloud Teledermatology SaMD.


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

[User]
Write a SDP section on change control and trend analysis for problems for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clauses 9.4, 9.6.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: Problem resolution for the MedRef Clinical Reference App integrates with change control per Clause 9.4 -- every correction is implemented as a controlled change with impact assessment and regression testing. Trends per Clause 9.6 are evaluated quarterly and at release readiness to identify systemic quality issues in the Clinical Drug Reference App.


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

"Verification activities follow IEC 62304 Clause 5.3.7 for user acceptance testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 5.3.7 which does not exist. Clause 5.3 has 5.3.1 through 5.3.6 only. The reference must be corrected to a valid clause number.


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

"IEC 62304:2022 Section 8.1 requires all software units to be verified."

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


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

"Software safety classification is performed per applicable regulatory requirements. The classification drives appropriate lifecycle activities and documentation."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "generic phrasing" provide no project-specific information about the NurseCall Hub patient call system dashboard. 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 SleepWell (sleep quality display app, Class A):

"The SleepWell employs Test-Driven Development with unit tests written before implementation."

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


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

[User]
Write a SDP section on change control process for HumidityMap Room Condition Logger, a Class A Environmental Condition Logger. Reference IEC 62304 Clauses 8.2, 8.2.1.
Network of IoT sensors logging temperature and humidity across hospital storage areas. Dashboard display for facility management.

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


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

[User]
Review this documentation excerpt for the HeartLink (cardiac telemetry system, Class B):

"The HeartLink lifecycle follows an industry-standard methodology ensuring compliance with applicable regulations. Phase gates are established at appropriate milestones."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "industry-standard", "appropriate milestones" provide no project-specific information about the HeartLink cardiac telemetry system. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Expand requirement SRS-FUNC-001: "output refresh interval for CalibrationTracker Equipment Logger" (Category: functional)
Project: CalibrationTracker Equipment Logger | Calibration Record System | Class A
Tracking calibration schedules and recording calibration results for compliance. Web application tracking calibration dates and results for medical test equipment. Administrative record keeping.

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

[Assistant]
Description: Output presentation on the REST API shall refresh at the configured interval, reflecting the most recent processed data from the Calibration Record System pipeline.
Rationale: Display freshness is critical for the Calibration Record System to provide actionable information to the user.
Priority: Mandatory
Acceptance Criterion: End-to-end latency from data acquisition to display update does not exceed the specified limit for 99.9% of samples.
Source: User need


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

[User]
Write a SDP section on configuration identification approach for WeatherNode Microclimate Station, a Class A Weather Station Firmware. Reference IEC 62304 Clauses 8.1, 8.1.1.
Solar-powered weather station firmware measuring temperature, humidity, wind, rainfall, and barometric pressure.

[Assistant] Content: The configuration identification scheme for the WeatherNode Microclimate Station assigns a unique identifier to every controlled artifact: source code modules, build configurations, documentation deliverables, and verification records. The scheme supports reconstruction of any released baseline of the Weather Station Firmware per Clause 8.1.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 InfuSafe Controller (insulin infusion pump controller, Class C):

"REQ-SRS-034: The InfuSafe Controller 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 SDP section on test records and acceptance criteria for Class B for DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clauses 5.6.7, 5.7.5.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: Integration test records for the DoseCalc Medication Calculator follow Clause 5.6.7, documenting the test cases executed, pass/fail results, anomalies found, and the software configuration tested. System test records follow Clause 5.7.5 with the same rigor. Acceptance requires all integration and system tests to pass, or all failures to be dispositioned with documented rationale.


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

[User]
Write a SDP section on development methodology for Class B for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clause 5.1.1.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: Development of the ThermoWatch Core Temperature Monitor proceeds through a V-model lifecycle where each development phase has a paired verification phase. For Class B, the mandatory verification phases are architecture verification, integration testing, and system testing. Detailed design verification is omitted, as Clause 5.4 activities are not required at this classification level.


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

"For the ChemoCalc, ISO 14971:2019 risk management is integrated with the IEC 62304 software lifecycle. Risk control measures identified in the risk analysis are incorporated as software requirements per Clause 5.2.3. The medical device risk analysis is re-evaluated per Clause 5.2.4 after requirements changes."

[Assistant]
Verdict: PASS
Note: Content correctly references ISO 14971:2019; 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 primary international standards applicable to development for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.1.2.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The HemaCount Digital Cell Counter development lifecycle is governed by IEC 62304:2006+AMD1:2015. Risk management follows ISO 14971:2019. The quality management system underpinning all activities conforms to ISO 13485:2016. Usability engineering for the IVD Digital Cell Counter Software interface adheres to IEC 62366-1:2015+AMD1:2020.


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

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

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

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the InfuSafe Controller (insulin infusion pump controller, Class C). Standards references are accurate.


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

[User]
Expand requirement SRS-FUNC-005: "alarm generation and notification" (Category: functional)
Project: NeoFeed Neonatal Feeding Pump | Neonatal Feeding Pump Firmware | Class C
Precise enteral feeding delivery for neonatal patients with sub-milliliter accuracy. Syringe pump firmware for precise enteral feeding in NICU patients. Flow accuracy is critical for extremely low birth weight infants.

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 NeoFeed Neonatal Feeding Pump shall generate audible and visual alarms within the specified response time when a monitored parameter exceeds its configured threshold.
Rationale: Alarm functionality is a safety-critical feature of the Neonatal Feeding Pump Firmware that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


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

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

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


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

[User]
Write a SRS section on requirements conventions and identification scheme for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clauses 5.2.1, 5.2.2.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: Each requirement for the PainRelief PCA Pump Controller is assigned a unique identifier and tagged with its type (functional, performance, interface, or safety) per Clause 5.2.2. Requirements are written in "shall" statements that are individually testable. The requirement set is baselined and controlled under the change management process.


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

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

"Maintenance activities follow ISO 14971-2 Clause 6."

[Assistant]
Verdict: FAIL
Note: The documentation references "ISO 14971-2" which is incorrect. ISO 14971 has no Part 2. ISO/TR 24971:2020 is a separate technical report. 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 NurseCall Hub (patient call system dashboard, Class A):

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

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


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

[User]
Write a SDP section on development methodology for Class C with full V-model for CochleaMap CI Fitting Software, a Class C Cochlear Implant Fitting Software. Reference IEC 62304 Clause 5.1.1.
Desktop software for fitting cochlear implant sound processors. Maps electrode activation levels and adjusts stimulation parameters.

[Assistant] Content: Class C rigor demands a full V-model for the CochleaMap CI Fitting Software Cochlear Implant Fitting Software. The descending arm covers requirements (Clause 5.2), architecture (Clause 5.3), detailed design (Clause 5.4), and implementation (Clause 5.5.1). The ascending arm covers unit verification (Clause 5.5), integration testing (Clause 5.6), and system testing (Clause 5.7), each independently reviewed.


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

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

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

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as needed", "appropriate milestones" provide no project-specific information about the VentAssist Pro ICU ventilator controller. 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 change control and trend analysis for problems for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clauses 9.4, 9.6.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: All TransVent Transport Ventilator problem corrections enter the change control process per Clause 9.4 before integration into the baseline. Trend analysis per Clause 9.6 tracks defect density, time-to-resolution, and defect category distribution across the Transport Ventilator Firmware development lifecycle to drive process improvement.


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

[Assistant] Content: The RetinaStim Visual Prosthesis Controller architecture isolates external dependencies behind abstraction interfaces per Clause 5.3.2. The RF coil to implant and external camera communication interfaces are accessed through adapter modules that translate protocol-specific details into the internal data model of the Retinal Prosthesis Controller 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 data format and interoperability requirements for PressoTrack Blood Pressure Trending, a Class B Ambulatory Blood Pressure Monitor Firmware. Reference IEC 62304 Clause 5.2.2.
Firmware for an automated blood pressure cuff that trends readings over 24 hours. Trending errors could mask hypertensive episodes.

[Assistant] Content: Interoperability requirements for the PressoTrack Blood Pressure Trending specify the data encoding, field definitions, and validation rules for all messages exchanged by the Ambulatory Blood Pressure Monitor Firmware. Each data interface has a defined schema, and the software rejects data that does not conform to the schema with appropriate error reporting.


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

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

"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 an IEC 62304 compliance reviewer. Evaluate the following documentation section and provide a verdict (PASS or FAIL) with a note explaining your assessment.

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

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

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


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

[Assistant] Content: The problem resolution process for the WeightAlert Neonatal Scale 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 Neonatal Scale Firmware 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-003: "source position encoder data capture and buffering" (Category: functional)
Project: BrachyDose HDR Afterloader Controller | HDR Brachytherapy Afterloader Firmware | Class C
Controlling radioactive source stepping positions and dwell times for high-dose-rate brachytherapy. Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

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

[Assistant]
Description: Data from the source position encoder shall be acquired by the BrachyDose HDR Afterloader Controller at the configured rate, with each sample timestamped and queued for processing.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Controlling radioactive source stepping positions and dwell times for high-dose-rate brachytherapy.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

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

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

[Assistant]
Description: The Cloud Teledermatology SaMD shall monitor all active parameters against user-configured thresholds and activate appropriate alarm signals when limits are breached.
Rationale: Alarm functionality is a safety-critical feature of the Cloud Teledermatology SaMD that directly supports clinical decision-making.
Priority: Mandatory
Acceptance Criterion: No alarm condition goes undetected across 200 simulated threshold exceedances with varying parameter values and crossing rates.
Source: Risk control


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

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

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

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


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

[User]
Write a SDP section on Class C classification justification and implications for PainRelief PCA Pump Controller, a Class C PCA Pump Controller Firmware. Reference IEC 62304 Clause 4.3.
Patient-controlled analgesia pump firmware allowing patient-initiated doses within physician-set limits. Overdose prevention is safety-critical.

[Assistant] Content: Safety classification analysis concluded that the PainRelief PCA Pump Controller is Class C under Clause 4.3. The PCA Pump Controller Firmware processes syringe position encoder and software failure during Patient-controlled analgesic delivery with lockout intervals and cumulative dose limits could cause serious harm. This is the highest-rigor classification in IEC 62304, requiring comprehensive documentation, unit testing with quantitative coverage targets, integration testing, system testing, and independent review of all verification outputs.


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

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

"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 CardioPulse Monitor.


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

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

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

[Assistant]
Description: The PathCloud AI Histology Analyzer shall encrypt patient-identifiable data at rest, ensuring that raw storage access cannot reveal protected health information.
Rationale: Data-at-rest encryption is required to meet privacy regulations and protect patient confidentiality.
Priority: Mandatory
Acceptance Criterion: Encrypted storage verified by reading raw storage media and confirming no patient-identifiable data is visible without the decryption key.
Source: Regulatory


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

[Assistant] Content: External interfaces of the PulseRing Smart Ring Monitor are architected as abstraction layers per Clause 5.3.2. The PPG LED array (green + red + IR) interface, BLE 5.3 protocol stack, and cloud sync API are encapsulated behind defined APIs, enabling the Wearable Smart Ring Firmware + Companion App to be tested with simulated external components.


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

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

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


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

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

[Assistant] Content: The CleanRoom Particle Counter Logger shall meet defined latency bounds for all safety-relevant processing paths. Throughput requirements specify the data rates the Cleanroom Environmental Logger must sustain from optical particle counter without data loss or processing backlog on Linux (Raspberry Pi).


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

[User]
Write a SDP section on development tools and tool qualification for Class A for ScheduleSync Appointment Manager, a Class A Appointment Scheduling System. Reference IEC 62304 Clause 5.1.4.
Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

[Assistant] Content: Development of the ScheduleSync Appointment Manager uses TypeScript/Next.js on Web SPA. Build automation ensures reproducible compilation, and all toolchain versions are recorded as part of the configuration management baseline. Given the Class A classification, no formal tool qualification report is produced; tool defects are handled through the standard problem resolution process.


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

"Risk management is performed in accordance with applicable standards and regulatory expectations. Hazard analysis is conducted as required by the regulatory framework."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "applicable standards", "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 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 verification includes white-box unit testing of all control flow paths and black-box system testing of all requirements."

[Assistant]
Verdict: FAIL
Note: Content mandates white-box 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. Only system testing is mandated.


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

[User]
Expand requirement SRS-DATA-001: "data integrity validation" (Category: data)
Project: ThermoWatch Core Temperature Monitor | Core Temperature Monitor Firmware | Class B
Continuous core body temperature monitoring with trend display and threshold alerts. Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

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 ThermoWatch Core Temperature Monitor shall validate the integrity of stored data using checksums, detecting and reporting any corruption of measurement records.
Rationale: Data integrity mechanisms ensure measurement records retrieved from the Core Temperature Monitor Firmware are trustworthy for clinical review.
Priority: Mandatory
Acceptance Criterion: Integrity check correctly identifies all corrupted records with zero false positives on uncorrupted data.
Source: System requirement


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

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

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

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


[System] You are 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 safety requirements for Class A -- confirms no safety functions for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clauses 5.2.2, 5.2.3.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

[Assistant] Content: Safety requirements are not applicable to the VitalBoard Patient Summary because the Class A Patient Summary Dashboard cannot contribute to a hazardous situation. The software does not implement risk control measures per Clause 5.2.3. All output is informational and used for Read-only display of patient vital sign history for clinical reference without clinical decision support.


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

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

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

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


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

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

"Software development follows IEC 62304 Clause 4.5 requirements for detailed design verification."

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


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

[User]
Write a SRS section on baseline security requirements for GaitSense Walking Analysis, a Class B Gait Analysis Insole Firmware. Reference IEC 62304 Clause 5.2.2.
Instrumented insole firmware analyzing gait patterns and detecting asymmetries. Reports generated for orthopedic assessment.

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

[User]
Write a SDP section on development platform and build infrastructure for TransVent Transport Ventilator, a Class C Transport Ventilator Firmware. Reference IEC 62304 Clause 5.1.4.
Portable transport ventilator firmware for ambulance and helicopter use. Must maintain ventilation under vibration and altitude changes.

[Assistant] Content: Source code for the TransVent Transport Ventilator Transport Ventilator Firmware is written in C (embedded) and compiled for STM32H7. The build pipeline is automated and deterministic -- identical source revisions produce identical binaries. All build tool versions are captured in the configuration baseline per Clause 5.1.4.


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

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

"Code reviews for the NurseCall Hub 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 SDP section on purpose and scope for Class A with minimal documentation for ScreenFlow Population Health Screener, a Class A Serverless Population Health Screening SaMD. Reference IEC 62304 Clause 5.1.1.
Serverless cloud application processing population-level health screening questionnaires and flagging individuals for follow-up based on risk scoring algorithms.

[Assistant] Content: This plan governs all software lifecycle activities for the ScreenFlow Population Health Screener Serverless Population Health Screening SaMD from requirements analysis through release, per IEC 62304 Clause 5.1.1. The Class A classification permits a reduced documentation set: verification is performed solely at the system level (Clause 5.7), and no unit-level or integration-level verification activities are planned.


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

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

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

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


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

[User]
Expand requirement SRS-SEC-002: "user identity verification" (Category: security)
Project: HemaCount Digital Cell Counter | IVD Digital Cell Counter Software | Class B
Automated white blood cell differential counting from digitized peripheral blood smear images. Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

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

[Assistant]
Description: Access to configuration and administrative functions of the IVD Digital Cell Counter Software shall be restricted to authenticated and authorized users.
Rationale: Unauthorized configuration changes to the IVD Digital Cell Counter Software could compromise its intended function or patient safety.
Priority: Mandatory
Acceptance Criterion: Brute-force protection activates after the specified number of failed authentication attempts.
Source: Risk control


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

[User]
Write a TRACE section on purpose and scope of the traceability matrix for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.7.1.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: Traceability for the PaceSet Pacemaker Programmer per Clause 5.7.1 links system requirements to software requirements, software requirements to design elements, and design elements to verification test cases. The matrix serves as the primary evidence that the Cardiac Pacemaker Programmer Software verification is complete and that no requirement is unaddressed.


[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: "authentication for configuration access" (Category: security)
Project: PathSlide Digital Pathology Viewer | Digital Pathology Viewer | Class A
Display of digitized pathology slides for reference viewing. Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

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 Digital Pathology Viewer shall be restricted to authenticated and authorized users.
Rationale: Access control prevents unauthorized modification of the Digital Pathology Viewer 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 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

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

[Assistant] Content: The IncidentReport Clinical Event Logger follows an agile-inspired iterative lifecycle with lightweight phase gates suited to Class A software. Milestones are Requirements Baseline, Implementation Freeze, and System Test Complete. No architecture review or detailed design review gate is required, as these artifacts are not mandated 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 NurseCall Hub (patient call system dashboard, Class A):

"SOUP is identified for the NurseCall Hub. SOUP anomaly lists are evaluated. SOUP is managed per the configuration management plan. SOUP items are documented. SOUP management follows IEC 62304."

[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 NurseCall Hub.


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

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

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


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

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

[Assistant] Content: Software safety classification for the InsuPrecise Insulin Pump Controller follows the procedure defined in IEC 62304 Clause 4.3. The classification considers whether the Insulin Pump Controller Firmware can contribute to a hazardous situation and, if so, whether external risk controls reduce the severity to non-serious injury. The result directly determines which IEC 62304 lifecycle activities are mandatory.


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

[User] Is IEC 60601-1:2005+AMD2:2020 a valid standard reference?

[Assistant] Yes. IEC 60601-1 is the general safety standard for medical electrical equipment. It has multiple sub-parts including 1-2 (EMC), 1-6 (usability), 1-8 (alarms), 1-10 (closed-loop), and 1-11 (home healthcare).


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

[Assistant] Content: Requirements for external system integration with the WeightAlert Neonatal Scale specify the API contracts, data formats, and error handling behavior for all outbound communication from the Neonatal Scale Firmware. The software must handle connection timeouts, malformed responses, and authentication failures without affecting safety-relevant functions.


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

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

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

[Assistant]
Description: The CardioCloud ECG Analysis Service memory footprint on GCP Kubernetes (GPU node pool) shall remain within specified limits under worst-case operational scenarios.
Rationale: Memory constraints are fixed by the GCP Kubernetes (GPU node pool) hardware and must be respected to prevent resource exhaustion during operation.
Priority: Mandatory
Acceptance Criterion: Memory profiling under stress conditions shows stable allocation with no leaks over a 72-hour test period.
Source: System requirement


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

[User]
Write a SDP section on change control and trend analysis for problems for BrachyDose HDR Afterloader Controller, a Class C HDR Brachytherapy Afterloader Firmware. Reference IEC 62304 Clauses 9.4, 9.6.
Firmware controlling high-dose-rate brachytherapy source positioning and dwell times. Source positioning errors cause lethal local radiation.

[Assistant] Content: Problem resolution for the BrachyDose HDR Afterloader Controller integrates with change control per Clause 9.4 -- every correction is implemented as a controlled change with impact assessment and regression testing. Trends per Clause 9.6 are evaluated quarterly and at release readiness to identify systemic quality issues in the HDR Brachytherapy Afterloader Firmware.