Traceability
One governed chain for TV-000118: 11 of 18 hops realized, 7 projected.
Meridian Medical SystemsNimbusPump NP-200 ProgramPSLF-03 · G3 openRelease FR-2026.1Effectivesince 15 Jan 2026
Chain coverage
| Segment | Count | Share |
|---|---|---|
| Realized | 11 | 61% |
| Projected | 7 | 39% |
Projected from Test onward
Hops stay projected until G3 clears VMR-0142 and PSCG-0042. Open PSLF-03
Walk the chain for TV-000118
Solid hops link into their module; dashed hops wait on upstream gates.
- CustomerM01Customer activeCUS-0001Meridian Medical Systems
- Product ecosystemM02ActivePRJ-2026-0042NimbusPump NP-200 Program
- Framework profileM03EffectivePFP-2026-0042Resolved product profile
- Lifecycle phaseM03Passed
- DeliverableM03ApprovedPSRA-0042Product Security Risk Assessment
- RequirementM03ApprovedPSPR-0042-SR-014Remote dosing commands mutually authenticated and integrity-protected
- Architecture elementM02BaselinedAE-000042Infusion dosing command processor
- ThreatM02Confirmed
- RiskM03Assessed
- Treatment / controlM02Adopted
- ImplementationM02ImplementingDC-000314Design control: authenticated command channel
- TestM02projectedNot startedVOB-000211Verification obligation: command interface fuzz test
- EvidenceM03projectedPendingEVD-000903Fuzz-test result package
- RetestM03projectedPendingRTS-000118Independent retest after remediation
- ApprovalM03projectedPendingG4-PRJ-2026-0042Verification accepted (G4)
- ReleaseM03projectedPendingREL-NP200-1.0NP-200 release baseline + Customer Security Package
- Post-market signalM03projectedNot startedSIG-pendingVulnerability / incident monitoring
- RetirementM03projectedNot startedEOL-pendingEnd-of-support & retirement
- 6. RequirementM03PSPR-0042-SR-014Remote dosing commands mutually authenticated and integrity-protectedApproved
- 11. ImplementationM02DC-000314Design control: authenticated command channelImplementing
- 12. TestM02VOB-000211Verification obligation: command interface fuzz testNot started
- 13. EvidenceM03EVD-000903Fuzz-test result packagePending
- 14. RetestM03RTS-000118Independent retest after remediationPending
- Framework rule
- Source, release, applicability rule, control objective, customer profile
- Requirement
- User need, rule, risk, control, test, evidence
- Architecture element
- Source file, baseline, interfaces, data classes, threats, controls
- Threat / risk
- Element, scenario, method, factors, owner, treatment, control, evidence
- Control
- Threats/risks, implementation, test, evidence, owner, status
- Evidence
- Source, test, environment, baseline, reviewer, integrity hash
- Post-market signal
- Affected product/version/component, risk, incident/patch, customer/regulatory actions