SourceFlag
Back to marketing opportunities
Human Verified marketing samplePublic official-source summary

Cloud

Inside a VA Secure DICOM Image-Sharing Solicitation

U.S. Department of Veterans Affairs, Network Contracting Office 16 · 36C25626Q1095

This SourceFlag sample shows how a proposal team can organize a dense healthcare IT solicitation into source-grounded requirements, risks, decisions, and open questions.

SourceFlag Team Human Verified the exact public summary shown here against the accepted public source package. This marketing page does not publish the full sample project or solicitation files. Confirm the controlling official source before acting.

Overview

The U.S. Department of Veterans Affairs, Network Contracting Office 16, issued this solicitation for a secure, bidirectional DICOM image and report exchange capability supporting VISN 16. The requirement reaches eight VA facilities and participating community-care partners, with work spanning interoperability, automation, onboarding, training, security evidence, operations, and pricing.

The source package is small, but the response problem is not. A notice and a 46-page attachment distribute important instructions across the price schedule, performance work statement, security clauses, quality-assurance plan, and quote instructions. The workspace keeps those parts connected instead of treating each section as a separate reading exercise.

What SourceFlag surfaced

A tightly defined response structure

The quote instructions call for a technical and management narrative capped at 15 pages, a past-performance volume capped at five pages with at least three relevant prime contracts, completed pricing for every base and option CLIN, B.1 administration information, FAR 52.212-3, and brand-name-or-equal literature with a salients crosswalk. Technical capability and management, past performance, and price are the three evaluation factors, but their relative importance is not stated.

Technical and operating commitments that need proof

The solicitation addresses VistA, CPRS, VistA Imaging, PACS, VA DICOM routers, automated search and prefetch, patient matching, community-partner onboarding, audit retention, uptime, support, and security controls. The review organized that material into 103 source-grounded requirements and separated response-stage evidence from post-award duties.

Conflicts that should stay visible

The package uses inconsistent wording for the volume containing B.1, the units for two CLINs, the fixed base-period start versus implementation within 150 days after award, the 60-day onboarding standard versus the QASP's 90-percent threshold, FedRAMP status, FIPS 140-3 versus a FIPS 140-2 minimum, and a security section marked “NA” even though detailed obligations follow.

Open inputs and questions

The workspace keeps open the amendment status, a referenced but missing Rules of Behavior Appendix E, undefined additional training, the Houston ship-to address versus distributed performance, any 24x7 support trigger, email-delivery mechanics, and evaluation weighting. Bidder-supplied facts remain placeholders, including the exact product and version, VA TRM status, FIPS, FedRAMP, and Section 508 evidence, small-business and SAM status, FAR 52.212-3, past performance, connection agreements, pricing, and the proposed technical approach. No official Q&A was included in the accepted source set.

Material exposure

The risk register flags possible rejection for missing CLIN pricing or inadequate brand-name-or-equal substantiation, along with a stated data-breach liquidated-damages provision of $37.50 per affected individual. These items are not filled in or resolved by SourceFlag Team; they remain visible for authorized customer and issuing-authority decisions.

How a proposal team could use this workspace

  • Work from a source-grounded brief and a nine-sheet workbook aligning submission tasks, required forms, evaluation factors, pricing instructions, risks, compliance requirements, post-award obligations, and the source register.
  • Use owner and reviewer placeholders while keeping response decisions tied to exact page, paragraph, table, and clause locators.
  • Build an outline, prepare clarification questions, reconcile pricing, identify bid or no-bid evidence gaps, and decide what must come from the customer before drafting proceeds.

What's included in the sample

  • A 44-page RFP brief and nine-sheet compliance workbook.
  • A structured workspace base, executive summary, and review-question register.
  • A source list plus a change report preserving the evidence trail.

Sample boundary

This sample is not a completed proposal, a compliance certification, or evidence that any bidder possesses the required capabilities.

Public page access does not expose the full matrix, detailed citations, assignments, raw solicitation files, or exports. Human Verified applies to this reviewed public summary. The editable trial project carries no persistent verified badge.