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

[User]
Expand requirement SRS-FUNC-002: "ADS1292R ECG AFE data capture and buffering" (Category: functional)
Project: CardioRhythm ECG Analyzer | Single-Lead ECG Device Firmware | Class B
Acquisition and preliminary rhythm classification of single-lead ECG for clinical screening. Portable ECG device firmware acquiring single-lead ECG and classifying basic rhythm types. Incorrect classification could delay 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: The CardioRhythm ECG Analyzer shall continuously sample ADS1292R ECG AFE data, buffer readings in memory, and pass validated samples to the processing module without data loss.
Rationale: Continuous data acquisition from the primary sensor is the fundamental input for Acquisition and preliminary rhythm classification of single-lead ECG for clinical screening.
Priority: Mandatory
Acceptance Criterion: Verified by test: software acquires sensor data continuously for 60 minutes without data loss, confirmed by comparing acquisition count against expected count at the configured sampling rate.
Source: System requirement


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

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

"Maintenance activities follow IEC 62304:2015 Clause 6."

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


[System] You are an IEC 62304 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 InfuSafe Controller (insulin infusion pump controller, Class C):

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

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "as appropriate", "best practices", "established procedures" provide no project-specific information about the InfuSafe Controller insulin infusion pump controller. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User] Does ISO 14971-1 exist?

[Assistant] No. ISO 14971 is a single-part standard. There is no Part 1 designation. The correct citation is ISO 14971:2019.


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-002: "user-configurable operating parameters" (Category: functional)
Project: InsuPrecise Insulin Pump Controller | Insulin Pump Controller Firmware | Class C
Automated insulin delivery control with programmable basal rates and bolus calculations. Embedded firmware controlling insulin delivery in a patch-type insulin pump. Incorrect dosing could cause severe hypoglycemia or diabetic ketoacidosis.

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

[Assistant]
Description: Operating parameters of the Insulin Pump Controller Firmware shall be user-configurable within validated ranges and stored in non-volatile memory.
Rationale: Configurable parameters allow the Insulin Pump Controller Firmware to be adapted to different clinical protocols and patient populations.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

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

[Assistant]
Verdict: FAIL
Note: Content mandates code coverage targets for Class A. IEC 62304 Class A requires only system-level verification (Clause 5.7). Coverage targets are Class B/C considerations. Class A has no coverage requirements.


[System] You are a regulatory 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 purpose of the SRS document for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.2.1.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: This Software Requirements Specification defines the functional, performance, and interface requirements for the HemaCount Digital Cell Counter IVD Digital Cell Counter Software. Requirements are derived from system requirements, the risk management file, and stakeholder needs analysis per IEC 62304 Clause 5.2.1. Each requirement is uniquely identified, prioritized, and traceable to its source.


[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: "user-configurable operating parameters" (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: Configuration changes to the RemotICU Continuous Monitoring Hub shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the Edge-to-Cloud ICU Monitoring Gateway to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: Configuration round-trip test: set, power-cycle, read-back for all parameters with 100% accuracy.
Source: User need


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

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

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

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


[System] You are 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 scope boundaries of the software system for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

[Assistant] Content: The software system boundary for NutriCalc TPN Formulation Tool encompasses the TPN Formulation Calculator application and its direct interfaces: desktop GUI, pharmacy system API. Components outside this boundary -- including external sensor hardware, manufacturing test fixtures, and third-party cloud services -- are addressed in the system-level risk analysis but are not governed by this plan.


[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: "startup diagnostic verification" (Category: functional)
Project: TeleRehab Remote Patient Monitor | Remote Rehabilitation Platform | Class B
Remote physiotherapy monitoring with exercise tracking and therapist-patient video sessions. Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

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

[Assistant]
Description: A power-on self-test shall validate IMU wearable communication, memory integrity, and WebRTC connectivity before the Remote Rehabilitation Platform transitions to its operational state.
Rationale: Startup verification prevents the Remote Rehabilitation Platform from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: All fault injection scenarios are detected with 100% reliability across 50 test iterations.
Source: System requirement


[System] You are a 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-004: "startup diagnostic verification" (Category: functional)
Project: OBDView Diagnostic Display | Vehicle Diagnostic Display App | Class A
Displaying vehicle diagnostic information from OBD-II interface for driver and mechanic use. Mobile app connecting to vehicle OBD-II port to display engine parameters, fault codes, and emissions data.

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

[Assistant]
Description: Upon power-up, the OBDView Diagnostic Display shall execute a self-test sequence verifying the integrity of the primary sensor interface, internal memory, and output subsystem before entering operational mode.
Rationale: Startup verification prevents the Vehicle Diagnostic Display App from operating with undetected faults that could affect output accuracy.
Priority: Mandatory
Acceptance Criterion: Self-test completes within the specified startup time and correctly detects each of the following injected faults: sensor disconnection, memory corruption, and display failure.
Source: System requirement


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

[User]
Write a SDP section on problem reporting and investigation for PathSlide Digital Pathology Viewer, a Class A Digital Pathology Viewer. Reference IEC 62304 Clauses 9.1, 9.2.
Web viewer for whole-slide digital pathology images. Pan, zoom, and annotation display. No AI-assisted diagnosis.

[Assistant] Content: Problems identified in the PathSlide Digital Pathology Viewer are reported per Clause 9.1 with anomaly description, affected component, severity, and reproduction steps. Investigation per Clause 9.2 determines root cause and impact. Relevant parties are advised per Clause 9.3 when the problem affects the Digital Pathology Viewer safety or regulatory compliance.


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

[User]
Expand requirement SRS-FUNC-007: "initialization integrity checks" (Category: functional)
Project: ScheduleSync Appointment Manager | Appointment Scheduling System | Class A
Administrative scheduling and calendar management for clinical appointments. Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

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

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


[System] You are 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 CardioPulse Monitor (cardiac rhythm monitor, Class B):

"For the CardioPulse Monitor, 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 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):

"SOUP is identified for the VentAssist Pro. 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 VentAssist 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 ChemoCalc (chemotherapy dose calculator, Class C):

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

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


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

[User]
Expand requirement SRS-DATA-001: "measurement data lifecycle" (Category: data)
Project: ConsentView Informed Consent Archive | Consent Document Viewer | Class A
Read-only viewing of archived informed consent documents. Web portal for patients and staff to view signed informed consent documents. Read-only document viewer.

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

[Assistant]
Description: Data retention in the ConsentView Informed Consent Archive shall meet the specified minimum duration, with oldest records overwritten only after the retention period expires.
Rationale: Data retention supports clinical trend analysis and regulatory requirements for record keeping associated with the Consent Document Viewer.
Priority: Mandatory
Acceptance Criterion: Oldest data record remains retrievable after continuous operation for the specified retention period.
Source: Regulatory


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

[User]
Write a SRS section on baseline security requirements for GrowthChart Pediatric Viewer, a Class A Growth Chart Display App. Reference IEC 62304 Clause 5.2.2.
Web app displaying pediatric growth charts with WHO/CDC percentile curves. Plots measurements, no diagnostic interpretation.

[Assistant] Content: The GrowthChart Pediatric Viewer Growth Chart Display App implements security controls per IEC 81001-5-1:2021: user authentication, role-based access control, encrypted storage, encrypted communications, and event logging. Security requirements are verified through system testing and documented in the security test report.


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

[User]
Write a SDP section on scope boundaries of the software system for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clauses 5.1.1, 5.1.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: Scope is limited to the CardioCloud ECG Analysis Service software items developed under this plan and released as a single configuration baseline. Peripherals, test jigs, and cloud infrastructure used during Automated arrhythmia detection and ECG interpretation as a cloud service for remote clinics are addressed by separate system-level documentation and are not governed by IEC 62304 Clause 5.1.1 activities described herein.


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

[Assistant] Content: The FactoryTemp Industrial Temperature Monitor Class A documentation plan produces five controlled documents: this SDP, the Software Requirements Specification, the System Test Plan and Report, the Software Release Record, and the Risk Management File. No additional verification documents are required for the Industrial Temperature Monitoring Firmware.


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

[User]
Write a SDP section on problem reporting and investigation for NutriCalc TPN Formulation Tool, a Class B TPN Formulation Calculator. Reference IEC 62304 Clauses 9.1, 9.2.
Desktop tool calculating total parenteral nutrition formulations based on patient metabolic needs and lab values.

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


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

[User]
Write a SDP section on verification strategy for Class A -- system testing only for HeartView Resting HR Display, a Class A Heart Rate Display Firmware. Reference IEC 62304 Clauses 5.7, 5.7.1.
Wearable firmware that shows resting heart rate on a small OLED screen. Read-only display with no arrhythmia detection or clinical alerts.

[Assistant] Content: Verification of the HeartView Resting HR Display consists exclusively of system-level testing per IEC 62304 Clause 5.7. Test cases derive from the software requirements specification and exercise the Heart Rate Display Firmware end-to-end on the ARM Cortex-M0+ platform. Unit-level verification (Clause 5.5) and integration testing (Clause 5.6) are not required for Class A software and are excluded from the verification scope.


[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 BreathEasy Air Quality Display, a Class A Environmental Air Quality Display. Reference IEC 62304 Clause 5.1.4.
Indoor air quality monitor displaying PM2.5, CO2, and temperature on an LCD. Informational display only with no clinical guidance.

[Assistant] Content: Source code for the BreathEasy Air Quality Display Environmental Air Quality Display is written in C++ (embedded) and compiled for ESP32-S3. 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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SDP section on purpose and scope for Class B with moderate documentation for DermaAssist Skin Lesion Classifier, a Class B Skin Lesion Classification App. Reference IEC 62304 Clause 5.1.1.
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 Software Development Plan defines the processes, tools, and deliverables governing development of the Skin Lesion Classification App in accordance with IEC 62304 Clause 5.1.1. Given the Class B safety classification -- where the software can contribute to a non-serious injury through AI-assisted classification of skin lesion images as benign or suspicious for dermatologist review -- this plan mandates architectural design documentation, integration testing, and software requirements traceability with sufficient rigor to mitigate identified risks.


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for SeismicWatch Earthquake Early Warning, a Class A Seismic Early Warning Firmware. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Firmware for a network of MEMS accelerometers providing earthquake early warning by detecting P-waves and estimating magnitude.

[Assistant] Content: Risk evaluation of SOUP in the SeismicWatch Earthquake Early Warning follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Seismic Early Warning Firmware. Anomalies relevant to Detecting seismic P-waves and providing early warning of potentially damaging earthquakes are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

[User]
Write a SRS section on system boundaries and external dependencies for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 5.2.2.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

[Assistant] Content: System boundaries for the SunGuard UV Index Display are defined at the software interface level. The UV Exposure Display Firmware receives input from VEML6075 UV sensor and produces output via I2C. Components beyond these interfaces are outside the scope of this SRS and are addressed in system-level documentation.


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

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

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

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


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

[User]
Write a THREAT section on system description for threat modeling for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.2.1.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The HemaCount Digital Cell Counter threat model system description per IEC 81001-5-1:2021 identifies the IVD Digital Cell Counter Software as the subject, with trust boundaries at each external interface. Assets include software integrity, data confidentiality, and service availability during Automated white blood cell differential counting from digitized peripheral blood smear images.


[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 AnticoagCalc INR Dose Adjuster, a Class B Anticoagulation Dosing Support Tool. Reference IEC 62304 Clauses 9.4, 9.6.
Web tool suggesting warfarin dose adjustments based on INR readings and patient history. Clinical decision support requiring physician review.

[Assistant] Content: All AnticoagCalc INR Dose Adjuster 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 Anticoagulation Dosing Support Tool development lifecycle to drive process improvement.


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

[User]
Expand requirement SRS-FUNC-005: "output refresh interval for ClinTrial EDC Platform" (Category: functional)
Project: ClinTrial EDC Platform | Clinical Trial EDC Web Platform | Class A
Electronic capture and management of clinical trial data across multiple investigator sites. Enterprise web platform for electronic data capture in multi-site clinical trials. Manages case report forms, randomization, and adverse event reporting.

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 Clinical Trial EDC Web Platform pipeline.
Rationale: Timely display updates ensure the user observes current readings without perceiving lag.
Priority: Mandatory
Acceptance Criterion: Measured display update interval is within 10% of the specified refresh period across 100 consecutive update cycles.
Source: User need


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

[Assistant] Content: The PowerTrack UPS Monitor review process is proportionate to the Class A risk level. The project lead reviews each deliverable for technical accuracy, and the quality representative verifies compliance with SOPs. Reviews are documented but do not require independent technical review of the UPS Monitoring Software verification activities.


[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 IncidentReport Clinical Event Logger, a Class A Incident Reporting System. Reference IEC 62304 Clauses 5.7, 5.7.4.
Web form for staff to submit clinical incident reports. Data entry and routing only, no analysis.

[Assistant] Content: System tests for the IncidentReport Clinical Event Logger are executed on the Web SPA target with the Incident Reporting System operating in its intended configuration. Test results are recorded per Clause 5.7.5, and the system test is verified complete per Clause 5.7.4 when all requirements have a linked passing test. No unit tests or integration tests are produced, as Class A does not require these verification levels.


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

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

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

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


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

[User]
Expand requirement SRS-SAFE-001: "Class A scope validation" (Category: safety)
Project: PostureGuard Desk Monitor | Posture Wellness Display Software | Class A
Visual feedback on desk posture for personal wellness awareness. USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

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 Posture Wellness Display Software software functions are limited to informational display and data presentation, with no capability to influence clinical decisions or therapeutic actions.
Rationale: Confirming the absence of safety-relevant functions validates the Class A classification under IEC 62304 Clause 4.3.
Priority: Mandatory
Acceptance Criterion: Architecture review demonstrates complete absence of safety-critical software functions in the Posture Wellness Display Software.
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 FMEA section on risk control measures and implementation for RadView DICOM Viewer, a Class A Medical Image Viewer. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Desktop application for viewing DICOM medical images. Display-only with standard windowing controls. No CAD or diagnostic measurement tools.

[Assistant] Content: Each risk control for the RadView DICOM Viewer per Clause 7.2.1 specifies the hazard addressed, the control mechanism, and the verification method. Controls implemented in software per Clause 7.2.2 are traced through the requirements-design-test chain to ensure complete implementation and verification in the Medical Image Viewer.


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

[User]
Write a SRS section on functional requirements overview for SunGuard UV Index Display, a Class A UV Exposure Display Firmware. Reference IEC 62304 Clause 5.2.2.
Wearable UV index monitor with an OLED display showing current UV exposure level. Informational only, no sunburn prevention claims.

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


[System] You are an IEC 62304 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 GlucoSpot Continuous Glucose Display, a Class B CGM Display App. Reference IEC 62304 Clause 5.3.2.
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 architecture defines error propagation rules at each interface per Clause 5.3.2. Invalid data from input sources 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 CGM Display App.


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

[User]
Review this documentation excerpt for the FetaSound (fetal heart rate monitor, Class B):

"The FetaSound Class B verification includes integration testing per Clause 5.6 and system testing per Clause 5.7. Integration tests verify inter-module interfaces. Statement coverage of at least 80% is targeted for unit tests where performed. The development team performs verification activities."

[Assistant]
Verdict: PASS
Note: Content correctly specifies Class B requirements. 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 RadBeam Planner (radiation therapy planning system, Class C):

"Compliance with IEC 62304 Clause 4.4 is demonstrated through security testing."

[Assistant]
Verdict: FAIL
Note: The documentation cites IEC 62304 Clause 4.4 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 SDP section on primary international standards applicable to development for BalanceBoard Vestibular Trainer, a Class B Balance Training Platform Firmware. Reference IEC 62304 Clause 5.1.2.
Force plate firmware measuring center-of-pressure excursions during balance exercises. Provides real-time visual biofeedback.

[Assistant] Content: Development of the BalanceBoard Vestibular Trainer software conforms to IEC 62304:2006+AMD1:2015 for the software lifecycle and ISO 14971:2019 for risk management integration. Quality management activities follow ISO 13485:2016, while usability engineering principles from IEC 62366-1:2015+AMD1:2020 inform the user interface design of the Balance Training Platform 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 MedImage PACS Viewer, a Class A Web PACS Image Viewer. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Web-based PACS viewer enabling radiologists to review DICOM images with standard tools (windowing, measurement, MPR). View-only, no AI or diagnostic processing.

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


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

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

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

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


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

[User]
Expand requirement SRS-FUNC-002: "configuration persistence and validation" (Category: functional)
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: Configuration changes to the ThermoWatch Core Temperature Monitor shall be validated against allowed ranges before acceptance and persisted to survive power loss.
Rationale: Parameter flexibility is essential for the Core Temperature Monitor Firmware to meet varying clinical requirements across deployment sites.
Priority: Mandatory
Acceptance Criterion: All configurable parameters persist correctly across power cycles and reject out-of-range values with appropriate error messages.
Source: User need


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

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

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

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


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

[User]
Write a SDP section on Class C classification justification and implications for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clause 4.3.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: Classification per IEC 62304 Clause 4.3 places the BreathSync ICU Ventilator Controller in Safety Class C. The ICU Ventilator Controller Software directly controls Automated mechanical ventilation with multiple modes, alarm management, and patient synchronization, and a software failure could result in serious injury or death without adequate external mitigation. Every IEC 62304 lifecycle activity applies, including unit verification with statement coverage >= 90%, branch coverage >= 80%, and MC/DC coverage >= 80%.


[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 PedDose Pediatric Dosing App, a Class B Pediatric Dosing Calculator App. Reference IEC 62304 Clause 5.2.2.
Mobile reference app for pediatric drug dosing with weight-based calculations and age-specific ranges.

[Assistant] Content: External dependencies of the PedDose Pediatric Dosing App include the Android operating environment, input hardware, and local drug database. The Pediatric Dosing Calculator App requirements assume these dependencies operate within their specified parameters; failure modes of external components are addressed in the risk analysis.


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

[User]
Write a SDP section on development methodology for Class B for FetalGuard Heart Rate Monitor, a Class B Fetal Heart Rate Monitor Firmware. Reference IEC 62304 Clause 5.1.1.
External fetal heart rate monitor firmware using Doppler ultrasound. Displays fetal heart rate and variability during labor.

[Assistant] Content: Development of the FetalGuard Heart Rate 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 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 TeleRehab Remote Patient Monitor, a Class B Remote Rehabilitation Platform. Reference IEC 62304 Clauses 7.1.2, 7.1.3.
Platform enabling remote physiotherapy with video consultations and wearable sensor data streaming. Generates exercise adherence reports.

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


[System] You are 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 regulatory framework for the WoundTrack references IEC 62304:2006+AMD1:2015 Clauses 4 through 9 as applicable to Class B software. ISO 14971:2019 governs the risk management process. The quality system operates under ISO 13485:2016."

[Assistant]
Verdict: PASS
Note: Content correctly specifies Class B requirements; uses the correct IEC 62304 citation; correctly references ISO 14971:2019. 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 risk control verification and traceability for VitalBoard Patient Summary, a Class A Patient Summary Dashboard. Reference IEC 62304 Clauses 7.3.1, 7.3.2.
Dashboard displaying patient vital signs history retrieved from the EMR. View-only with no alerting or trend analysis.

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


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

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

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


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

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

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

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


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

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

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

[Assistant]
Description: The IncidentReport Clinical Event Logger memory footprint on Web SPA shall remain within specified limits under worst-case operational scenarios.
Rationale: Exceeding memory limits could cause undefined behavior in the Incident Reporting System, potentially affecting safety.
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 an IEC 62304 regulatory documentation expert. Generate precise, class-appropriate content for medical device software documentation.

[User]
Write a SRS section on enhanced security for Class B and C for HemaCount Digital Cell Counter, a Class B IVD Digital Cell Counter Software. Reference IEC 62304 Clause 5.2.2.
Desktop software performing automated differential white blood cell counting on digitized blood smear images using computer vision.

[Assistant] Content: The Class B/C HemaCount Digital Cell Counter requires enhanced security controls beyond baseline requirements. The IVD Digital Cell Counter Software implements mutual authentication for all external interfaces, firmware integrity verification at startup, and secure update mechanisms. Vulnerability management follows IEC 81001-5-1:2021 throughout the product lifecycle.


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

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

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

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


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

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

"IEC 62304-5 Section 7.1 requires all software units to be verified."

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


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

[User]
Write a SAD section on external interface architecture for BreathSync ICU Ventilator Controller, a Class C ICU Ventilator Controller Software. Reference IEC 62304 Clause 5.3.2.
Software controlling an ICU mechanical ventilator with multiple ventilation modes (volume, pressure, SIMV). Failure could result in patient death.

[Assistant] Content: External interface architecture for the BreathSync ICU Ventilator Controller ICU Ventilator Controller Software wraps each physical interface in an abstraction layer. This design per Clause 5.3.2 decouples the application logic from hardware specifics of Dual ARM Cortex-R52 (ASIL-D), enabling integration testing with simulated interfaces.


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

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

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


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

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

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

[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 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 is designed to meet all applicable performance criteria. System requirements are addressed through appropriate design activities."

[Assistant]
Verdict: FAIL
Note: The documentation section contains generic filler. Phrases like "generic phrasing" provide no project-specific information about the SleepWell sleep quality display app. Content must reference specific IEC 62304 clauses, concrete activities, and measurable criteria.


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for VisitorPass Access Management, a Class A Visitor Management System. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Kiosk application for visitor registration and badge printing in hospital lobbies. Administrative access control.

[Assistant] Content: The VisitorPass Access Management SOUP risk assessment per Clause 7.1.3 documents all known SOUP defects relevant to the Visitor Management System operational context. Where a SOUP defect could contribute to a hazardous situation, the architecture implements a software-level mitigation or the affected SOUP component is replaced.


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

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

[Assistant] Content: SOUP components in the IncidentReport Clinical Event Logger are catalogued per Clause 8.1.2 with title, version, supplier, and license terms. The risk management process evaluates each SOUP item's known anomaly list per Clause 7.1.3 to determine whether any published defect could contribute to a hazardous situation in the Incident Reporting System.


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

[User]
Write a SDP section on Class A classification justification and implications for MedRef Clinical Reference App, a Class A Clinical Drug Reference App. Reference IEC 62304 Clause 4.3.
Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

[Assistant] Content: Under IEC 62304 Clause 4.3, the MedRef Clinical Reference App is classified as Safety Class A. The Clinical Drug Reference App is a purely informational system for Providing searchable drug information and interaction warnings for clinical reference without making prescribing decisions with no control over therapeutic delivery, diagnostic decision-making, or life-sustaining functions. Software failure would result in loss of informational display, not patient harm.


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

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

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

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


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

[User]
Write a SAD section on SOUP risk evaluation and anomaly management for ThermoWatch Core Temperature Monitor, a Class B Core Temperature Monitor Firmware. Reference IEC 62304 Clauses 5.3.3, 7.1.3.
Continuous core temperature monitoring firmware using an ingestible sensor pill. Displays temperature trend with configurable alerts.

[Assistant] Content: Risk evaluation of SOUP in the ThermoWatch Core Temperature Monitor follows Clause 7.1.3. Published anomaly lists are reviewed for each SOUP item deployed in the Core Temperature Monitor Firmware. Anomalies relevant to Continuous core body temperature monitoring with trend display and threshold alerts are entered into the risk management file, and mitigations are implemented where the residual risk is unacceptable.


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

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

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

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

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

[User]
Write a FMEA section on risk control measures and implementation for SurgLog Procedure Documentation App, a Class A Surgical Documentation App. Reference IEC 62304 Clauses 7.2.1, 7.2.2.
Tablet app for surgeons to dictate and review surgical procedure notes. Documentation tool only, no clinical decision support.

[Assistant] Content: The SurgLog Procedure Documentation App risk controls per Clause 7.2.1 address each failure mode with unacceptable residual risk. Software-implemented controls per Clause 7.2.2 include defensive coding measures, plausibility checks, and safe-state transitions. Each control is documented as a software requirement and verified for the Surgical Documentation App.


[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 DoseCalc Medication Calculator, a Class B Medication Dose Calculator App. Reference IEC 62304 Clauses 9.4, 9.6.
Mobile app calculating medication doses based on patient weight, age, and renal function. Incorrect calculations could cause underdosing or adverse effects.

[Assistant] Content: Corrections to the DoseCalc Medication Calculator follow the change control process per Clause 9.4, with regression testing proportional to the scope of the change. Problem reports are periodically analyzed for trends per Clause 9.6 to identify systemic issues in the development process that might affect the quality of the Medication Dose Calculator 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 change control and trend analysis for problems for PostureGuard Desk Monitor, a Class A Posture Wellness Display Software. Reference IEC 62304 Clauses 9.4, 9.6.
USB webcam software that estimates sitting posture and displays a wellness score. No ergonomic prescriptions or clinical assessments.

[Assistant] Content: Corrections to the PostureGuard Desk Monitor follow the change control process per Clause 9.4, with regression testing proportional to the scope of the change. Problem reports are periodically analyzed for trends per Clause 9.6 to identify systemic issues in the development process that might affect the quality of the Posture Wellness Display Software.


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

"IEC 62304 Clause 5.0 requires the WoundTrack to implement security testing."

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


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

[Assistant] Content: The TrainCert Staff Certification Tracker risk management process is concurrent with development, not sequential. Software causes of hazardous situations are identified per Clause 7.1 and documented per Clause 7.1.4. Risk controls are implemented as software requirements and verified through the applicable testing levels for the Training Certification System.


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

"Configuration management for the HeartLink follows Clause 8. Configuration items are identified per Clause 8.1.1, SOUP is identified per Clause 8.1.2, and change control is managed per Clause 8.2. Status accounting is maintained per Clause 8.3."

[Assistant]
Verdict: PASS
Note: Content content is appropriate for the HeartLink (cardiac telemetry system, Class B). Standards references are accurate.


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

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

"Maintenance activities follow ISO 14901 Clause 6."

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


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

[User]
Expand requirement SRS-FUNC-006: "startup diagnostic verification" (Category: functional)
Project: MedRef Clinical Reference App | Clinical Drug Reference App | Class A
Providing searchable drug information and interaction warnings for clinical reference without making prescribing decisions. Standalone mobile app providing searchable drug reference database with interaction checker. Display-only — no prescription or dosing decisions.

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

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


[System] You are a regulatory 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 PainScale Digital Assessment Tool, a Class B Pain Assessment Tool. Reference IEC 62304 Clause 5.1.2.
Web app for standardized pain assessment using validated scales (VAS, NRS, McGill). Records longitudinal pain data for treatment monitoring.

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


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

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

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

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


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

[User]
Write a SRS section on functional requirements overview for FleetTrack GPS Tracking Module, a Class A Fleet GPS Tracking Firmware. Reference IEC 62304 Clause 5.2.2.
Embedded firmware for a fleet vehicle GPS tracking module. Reports position, speed, and geofence events to a central server.

[Assistant] Content: Functional requirements for the FleetTrack GPS Tracking Module are derived from the system requirements for Real-time GPS tracking and geofence monitoring of fleet vehicles and from risk control measures identified in the ISO 14971 analysis. Each requirement specifies a single function of the Fleet GPS Tracking Firmware with measurable acceptance 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 StepTrack (wellness pedometer app, Class A):

"System testing for the StepTrack verifies that all software requirements are met in the operational environment. Test failures trigger the software problem resolution process per Clause 9. No unit-level or integration-level tests are required for this Class A wellness pedometer app."

[Assistant]
Verdict: PASS
Note: Content correctly limits Class A to system-level verification. 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 THREAT section on system description for threat modeling for PaceSet Pacemaker Programmer, a Class C Cardiac Pacemaker Programmer Software. Reference IEC 62304 Clause 5.2.1.
Desktop software for interrogating and programming cardiac pacemakers via telemetry wand. Incorrect programming could cause pacing failure.

[Assistant] Content: The PaceSet Pacemaker Programmer threat model scope encompasses the Cardiac Pacemaker Programmer Software, its communication interfaces (proprietary RF, USB, display), stored data, and the operational environment. Data flows between the RF telemetry wand and the application logic, and between the application and display are analyzed for potential security threats.


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

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

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


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

[User]
Write a SRS section on sensor and communication protocol requirements for LabView Results Portal, a Class A Laboratory Results Viewer. Reference IEC 62304 Clause 5.2.2.
Web application displaying laboratory test results retrieved from the hospital LIS. Read-only viewer with no result interpretation or flagging.

[Assistant] Content: The LabView Results Portal communication interfaces include HL7 FHIR API, HTTPS connecting the Laboratory Results Viewer to external systems and sensors. Each interface requirement specifies the expected behavior under normal operation and the response to communication failure conditions.


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

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

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

[Assistant]
Description: The PainScale Digital Assessment Tool shall log measurement data with timestamps to non-volatile storage and provide a mechanism to retrieve logged data via web form.
Rationale: Persistent measurement records enable post-hoc analysis and meet regulatory requirements for data retention.
Priority: Desirable
Acceptance Criterion: Data retrieval produces complete, uncorrupted records for the full specified retention period.
Source: User need


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

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

"Software maintenance is planned. Software maintenance activities are defined. The maintenance plan covers all aspects. Maintenance follows the plan. The CaloriePal 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 CaloriePal.


[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 DoseLog Radiation Badge Reader, a Class A Dosimetry Data Logger. Reference IEC 62304 Clause 5.1.2.
Desktop software reading and archiving personal radiation dosimeter data. Records exposure history for occupational health compliance.

[Assistant] Content: The software lifecycle for the DoseLog Radiation Badge Reader is executed under IEC 62304:2006+AMD1:2015, with risk management per ISO 14971:2019 integrated at each phase gate. Quality system requirements follow ISO 13485:2016, and usability validation of the Dosimetry Data Logger follows IEC 62366-1:2015+AMD1:2020.


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

[User]
Write a SDP section on primary international standards applicable to development for CardioCloud ECG Analysis Service, a Class B Cloud ECG Analysis SaMD. Reference IEC 62304 Clause 5.1.2.
Cloud SaaS platform receiving 12-lead ECG recordings from clinics, running automated arrhythmia detection, and returning annotated results via FHIR API.

[Assistant] Content: The CardioCloud ECG Analysis Service 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 Cloud ECG Analysis SaMD interface adheres to IEC 62366-1:2015+AMD1:2020.


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

[User]
Expand requirement SRS-INTF-001: "sensor data link requirements" (Category: interface)
Project: ScheduleSync Appointment Manager | Appointment Scheduling System | Class A
Administrative scheduling and calendar management for clinical appointments. Web application for scheduling patient appointments across multiple clinics. Administrative scheduling only, no clinical workflow.

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

[Assistant]
Description: Communication with the primary sensor over REST API shall include CRC-based error detection, automatic retry, and graceful degradation on persistent failure.
Rationale: Reliable sensor communication is the foundation of the Appointment Scheduling System data acquisition pipeline.
Priority: Mandatory
Acceptance Criterion: Communication operates without data loss for 72 hours continuously, with automatic recovery from simulated failures within the specified time.
Source: System requirement


[System] You are a 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] Can I cite IEC 62304-2 in my documentation?

[Assistant] No. IEC 62304 has no Part 2. It is a single-part standard. The correct citation is IEC 62304:2006+AMD1:2015.


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

[User]
Write a SRS section on baseline security requirements for AutoclaveLog Cycle Recorder, a Class A Sterilization Cycle Data Logger. Reference IEC 62304 Clause 5.2.2.
PC software recording autoclave cycle data (time, temperature, pressure) and generating compliance reports.

[Assistant] Content: Baseline security requirements for the AutoclaveLog Cycle Recorder ensure the Sterilization Cycle Data Logger protects user data, resists unauthorized access, and maintains audit trails. Data communicated via database is encrypted. Access is controlled through authentication mechanisms appropriate to the deployment environment.


[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 RemotICU Continuous Monitoring Hub, a Class B Edge-to-Cloud ICU Monitoring Gateway. Reference IEC 62304 Clause 5.3.2.
Edge gateway collecting data from bedside monitors (SpO2, HR, BP, ventilator) and streaming to cloud for trending, alerting, and tele-ICU review.

[Assistant] Content: The RemotICU Continuous Monitoring Hub architecture prevents error propagation by requiring input validation at every software item boundary per Clause 5.3.2. When a software item detects invalid input, it transitions to a defined error state and notifies the error management subsystem. The Edge-to-Cloud ICU Monitoring Gateway maintains safe operation during error recovery.


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

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

[Assistant] Content: The TeleRehab Remote Patient Monitor threat model decomposes the Remote Rehabilitation Platform into data flow diagrams showing all external entities, processes, data stores, and data flows. Each data flow crossing a trust boundary is analyzed for threats. The decomposition covers IMU wearable input, internal processing, and output via WebRTC.


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

[Assistant] Content: The purpose of this traceability matrix is to confirm complete coverage of the ClinTrial EDC Platform software requirements through design and verification per Clause 5.7.1. Bidirectional tracing enables identification of gaps (unimplemented requirements) and orphans (implementations without requirements) in the Clinical Trial EDC Web Platform.


[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: "alarm generation and notification" (Category: functional)
Project: GlucoSpot Continuous Glucose Display | CGM Display App | Class B
Displaying continuous glucose monitor readings with trend analysis and glucose range alerts. Mobile app receiving and displaying continuous glucose monitor readings via BLE. Shows trends, time-in-range, and configurable glucose 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: Alarm thresholds shall be configurable per clinical protocol. The GlucoSpot Continuous Glucose Display shall trigger alerts within the maximum allowable latency of a threshold crossing.
Rationale: Timely alarm generation is essential for the CGM Display App to alert clinicians to abnormal conditions requiring intervention.
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 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: DermaAssist Skin Lesion Classifier | Skin Lesion Classification App | Class B
AI-assisted classification of skin lesion images as benign or suspicious for dermatologist review. Mobile app using a CNN to classify skin lesion images as benign/suspicious. Decision support requiring dermatologist confirmation.

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 Skin Lesion Classification App shall support bidirectional data exchange with external systems over camera API.
Rationale: External system connectivity is required for the Skin Lesion Classification App to function within the broader clinical infrastructure.
Priority: Desirable
Acceptance Criterion: Format validation passes for all message types with correct field encoding verified.
Source: User need