Qs and As Solicitation No. 2011-N-13520 CDA 2nd set.doc

Solicitation No. 2011-N-13520, Clinical Document Architecture (CDA)

Questions and Answers (2nd set)

1. Solicitation document, Section E.1.3: Regarding file extensions

The Budget file extension is listed as “xl”; should this be “xls”? Answer: Yes.

2. What file format would you prefer for the SF 1449? Would we be able to submit the signed SF 1449 as a pdf? In how would you like the SF 1449 named? Answer: Pdf is fine for the 1449 and just name it 1449.

3. Solicitation document, Section E.1.4 Are we able to use a smaller font size than 11 pt in tables, charts and graphics? Answer: Yes, you can, but make sure the smaller font is legible and no special instrument is required to read.

4. Experience/Past Performance Matrix. Can we use a different format for the Experience/Past Performance information than the chart provided, as long as we supply the same information? i.e., “portrait” as opposed to “landscape”. Answer: You can use a different format to list experience/past performance, but must include the information requested.

5. Are we required to have all of the Experience/Past Performance in one chart, or could we have each Experience/Past Performance reference in a separate chart? Answer To verify past performance we contact references from clients or former clients. Although there will be two separate evaluations, the idea of the matrixor chart is to contact the same clients listed for experience. Therefore, one chart for both is required.

6. Can you either provide more information or provide a link that can provide more information on Green Clip Pilot referenced in Task 0001? Answer: All generic Green CDA documentation is available from the HL7 website www.hl7.org. The work specifically is to continue supporting a pilot of a green version of Central Line Insertion Practices (CLIP) data with one or two vendors. The XSLT transformations have already been developed and tested for the Green CLIP pilot. This work would be to provide technical assistance and/or bug fixes as needed with implementers in the pilot.