Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF FEBRUARY 17, 2017 FBO #5565
SOURCES SOUGHT

T -- Drug Information Source for MedlinePlus

Notice Date
2/15/2017
 
Notice Type
Sources Sought
 
NAICS
511199 — All Other Publishers
 
Contracting Office
Department of Health and Human Services, National Institutes of Health, National Library of Medicine, 6707 Democracy Blvd., Suite 105, Bethesda, Maryland, 20894, United States
 
ZIP Code
20894
 
Solicitation Number
NIHLM2017948MM
 
Archive Date
3/14/2017
 
Point of Contact
Maryann Meza, Phone: 3014517329
 
E-Mail Address
maryann.meza@nih.gov
(maryann.meza@nih.gov)
 
Small Business Set-Aside
Total Small Business
 
Description
This is a Small Business Sources Sought notice. The NAICS code for this Small Business Sources Sought notice is: 511199-All Other Publishers. This is NOT a solicitation for proposals, proposal abstracts, or quotations. The purpose of this notice is to obtain information regarding: (1) the availability and capability of qualified small business sources; (2) whether they are small businesses; HUBZone small businesses; service-disabled, veteran-owned small businesses; 8(a) small businesses; veteran-owned small businesses; woman-owned small businesses; or small disadvantaged businesses; and (3) their size classification relative to the North American Industry Classification System (NAICS) code for the proposed acquisition. Your responses to the information requested will assist the Government in determining the appropriate acquisition method, including whether a set-aside is possible. An organization that is not considered a small business under the applicable NAICS code should not submit a response to this notice. All responsible sources may submit a capability statement which will be considered by the National Library of Medicine. This Sources Sought Notice is not a Request for Quotations (RFQ), nor is an RFQ available. The capability statement should contain enough sufficient detail for the Government to make an informed decision regarding your capabilities; however, the statement should not exceed 6 pages (excluding attachments.) Interested firms responding to this Sources Sought Notice must provide a capability statement that displays the following: (a) Microsoft Word or PDF file in 12 point font; (b) DUNS number, organization name, address, point of contact, and size and type of business (e.g., 8(a), HUBZone, etc) pursuant to the applicable NAICS code); (c) Technical and administrative points of contact, including names, titles, addresses, telephone and fax numbers, and e-mail addresses; (d) Staff expertise, including their availability, experience, and formal and other training; (e) Current in-house capability and capacity to perform the work; (f) Prior completed projects of similar nature; (g) Corporate experience and management capability; and (h) Examples of prior completed Government contracts, references, and other related information. This sources sought notice requires capability statements to be submitted via eCPS.: 1) Electronic copy via the NLM electronic Contract Proposal Submission (eCPS) website at https://ecps.nih.gov/NLM. For directions on using eCPS, go to https://ecps.nih.gov/NLM/home/howto NOTE: To submit your electronic capability statement using eCPS, all offerors must have a valid NIH External Directory Account, which provides authentication and serves as a vehicle for secure transmission of documents and communication with the NLM. The NIH External Directory Account registration process may take up to 24 hours to become active. Submission of proposals by facsimile or e-mail is not accepted. All capability statements must be submitted electronically no later than 10:00am Eastern time on February 27th, 2017 via the method indicated above. Disclaimer and Important Notes: This notice does not obligate the Government to award a contract or otherwise pay for the information provided in response. The Government reserves the right to use information provided by respondents for any purpose deemed necessary and legally appropriate. Any organization responding to this notice should ensure that its response is complete and sufficiently detailed to allow the Government to determine the organization's qualifications to perform the work. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. After a review of the responses received, a pre-solicitation synopsis and solicitation may be published in Federal Business Opportunities. However, responses to this notice will not be considered adequate responses to a solicitation. Confidentiality: No proprietary, classified, confidential, or sensitive information should be included in your response. The Government reserves the right to use any non-proprietary technical information in any resultant solicitation(s). -------------------------------------------- DRAFT STATEMENT OF WORK Drug Information Source for MedlinePlus 1. Background Information To assist consumers in obtaining the information they need to make informed decisions about health and wellness, the National Library of Medicine (NLM) has developed MedlinePlus (http://medlineplus.gov), an easily understandable Web resource for the public. MedlinePlus contains and links to information from authoritative health Web sites and content providers, especially those from the National Institutes of Health. NLM makes MedlinePlus available to the public through a variety of MedlinePlus-branded Web sites, Web services, Web applications, APIs, email and social media communications, XML files and search results. 2. Purpose and Objectives of the Procurement NLM intends to license drug information in English and Spanish to assist the public in locating information about prescription and over-the-counter medications via MedlinePlus. "MedlinePlus" means all MedlinePlus branded full and mobile Web sites, Web services, Web applications, APIs, email and social media communications, XML files and search results. 3. Mandatory Content Requirements 1. At least 1,000 English monographs. 2. Equivalent content in Spanish. 3. The ability to identify equivalent English and Spanish monographs. The vendor must describe how they associate equivalent English and Spanish monographs within the data provided for each monograph. 4. The ability to toggle between all English and Spanish monographs at the individual, equivalent monograph level. 5. Coverage of both prescription and over-the-counter medications. 6. Coverage of both single ingredient medications and combination ingredient medications. 7. Each monograph must include the ingredient (generic) name for the medication that is used in the United States, alternate or synonymous medication names, when applicable, and associated brand names and brand names of combination products used in the United States. 8. A stand-alone file that maps all of the relevant RxNorm Concept Unique Identifiers (RXCUIs), including, at a minimum, all relevant Semantic Clinical Dose Form (SCDF) RXCUIs, to each monograph. The file must include, at a minimum, the monograph ID, the English monograph name, the SCDF RXCUI and the SCDF RXCUI name. If the English and Spanish monograph IDs are not identical for equivalent English/Spanish monographs, then the file must also include both the English monograph ID and the Spanish monograph ID and must indicate the equivalent relationship between the two. The file must be delivered at the same time as the monograph updates, and the file must reflect the most recent monograph content. RXCUI mappings embedded within each individual monograph XML file are also acceptable. Embedded mappings must also include, at a minimum, all relevant Semantic Clinical Dose Form (SCDF) RXCUIs for the given monograph. 9. We expect that RXCUI mappings will be identical for the equivalent English & Spanish monographs. If there is ever a circumstance where the mapping would differ between the equivalent English & Spanish monographs, the vendor must describe this circumstance and how they handle it from an editorial perspective and within the stand-alone mapping file or embedded mappings. 10. The vendor must explain their process of mapping monographs to RXCUIs and their process for updating and maintaining those mappings. 11. All content must be free of commercial endorsements or advertisements. 12. The vendor must describe the typical contents of each monograph or each class of monograph if there are multiple classes of them. Contents may include, but are not limited to, information on why a medication is prescribed, how it is used, precautions, side effects, interactions, storage, missed doses and overdose information. The vendor must list the topics or sections that they cover on each monograph and describe the contents of those topics/sections. 13. The vendor must describe their process for keeping monograph content up to date. 14. The vendor must describe how they keep up with, display, and make editorial decisions about FDA warnings at the monograph level for both English and Spanish monographs. Examples of warnings include, but are not limited to, safety alerts, ongoing safety reviews, safety communications and notices of withdrawal from market. 15. The vendor must address whether or not they provide FDA approval status at the monograph level. 16. The intended audience for the monographs must be general health information consumers in the United States. The vendor must describe how they address the needs of a U.S. consumer audience in their writing and in their editorial policies. 17. Monographs must be written in consumer friendly language. In the response, the vendor must indicate the reading or grade level. The vendor must include the measurement scale used to determine the reading or grade level. 18. Spanish monographs must be in culturally neutral Spanish appropriate for a U.S. consumer audience, not written or narrated in the style or vocabulary of a particular Spanish nationality. The vendor must describe their translation procedures, including quality control procedures. 19. The vendor must deliver updated monograph and mapping file content to NLM at least once a month. The response must include the vendor's regular update schedule and a description of the content of the update and the delivery mechanism. 20. When NLM identifies major content issues, NLM will communicate the issue with the vendor. The vendor must describe their procedure and turn-around time for content updates, including procedures and timelines for emergency content updates. 21. NLM will forward to the vendor any feedback received from users regarding content. The vendor must describe their procedure for reviewing this feedback, incorporating this feedback into their editorial cycle, and following-up with NLM on any action taken. Preferred Content Features (not mandatory) 1. Within the stand-alone file that maps all of the relevant RXCUIs or within the RXCUIs embedded in the individual monograph XML files, additional RXCUI mappings of the following term types may be included for each monograph. Note: SCDF mappings are required. See "Mandatory Content Requirements" above. a) BPCK - Brand Name Pack b) BN - Brand Name c) SCDC - Semantic Clinical Drug Component d) SCD - Semantic Clinical Drug e) SBD - Semantic Branded Drug f) SBDC - Semantic Branded Drug Component g) GPCK - Generic Pack h) SBDF - Semantic Branded Drug Form 2. If the vendor provides the RXCUI mappings in a stand-alone file, the stand-alone file includes the Spanish monograph name for each entry. 3. A pronunciation guide for the monograph name (ingredient/generic name). 4. Pill images with meaningful alt text in both English and Spanish. The vendor must provide an identifier for linking the pill images to the appropriate English & Spanish monographs. If the vendor offers pill images, they must include at least 5 sample images with their proposal. The vendor must also describe or demonstrate how they associate individual pill image files to individual English and Spanish monograph XML files. The pill images must be delivered at the same time as the monograph updates, and the pill images must reflect the most recent monograph content. 5. Citations or references, with PubMed links, in each monograph. 6. Relative links to other monographs in the collection. 7. Indicate any other special features available. 4. Mandatory Technical Requirements 1. Delivery of monographs in well-formed, valid XML format with an accompanying DTD. 2. Delivery of individual XML files for each monograph in each language - One XML file for the English monograph and a separate XML file for the equivalent Spanish monograph. 3. Delivery of monograph-to-SCDF RXCUI mappings in a stand-alone CSV or XML file (XML is preferred but CSV is acceptable) or embedded within each individual monograph XML file. 4. Allow NLM to host all of the vendor-provided content on NLM servers, including pill images, if applicable. 5. Allow for MedlinePlus co-branding on drug information pages. 6. The awardee will be required to provide NLM with technical support and advanced delivery of the content files within 2 weeks of being selected by NLM so that NLM can implement the co-branded content pages and links to these pages on MedlinePlus-branded sites, services and files. 7. When NLM identifies major technical issues, NLM will communicate the issue with the vendor. The vendor must describe their procedure and turn-around time for technical fixes, including procedures and timelines for emergency fixes. 8. Accessibility of content: All electronic content must meet Section 508 Guidelines. See the more specific requirements below regarding Section 508 Compliance. 6. Additional Requirements 1. Features and product offerings will be evaluated as they exist at the time of proposal submission. Beta releases and planned updates will not be considered. 2. Include the cost for licensing this product. The cost must be an annual flat fee for providing the content to users of any MedlinePlus branded Web site, the ability for end-users of MedlinePlus-branded sites to print, email and share links to the content for individual, personal use, and for providing links to the content on any MedlinePlus branded Web service, Web application, API, email and social media communication, XML file and search result. 3. Include a sample license agreement governing the use of the content on all MedlinePlus-branded Web sites, Web services, Web applications, APIs, email and social media communications, XML files and search results. The license agreement must also address NLM's rights related to the sharing of links to the content on MedlinePlus-branded sites, services, applications, communications, files and search results. 4. Include your copyright statement and any required disclaimers in both English and Spanish. 5. If the vendor requires their logo to be displayed on all vendor-supplied content pages, the logo must be smaller than 70x70 pixels and NLM must be allowed to determine the placement of the logo on the content pages. Include a sample of the logo (in English and Spanish if the logo differs in each language) and any display requirements. 6. Provide a list of at least three other organizations that license the content, along with accompanying Web site URLs. Provide at least three references that NLM can contact. 7. Provide a copy of your customer service policy, or other evidence of your commitment to customer service. 8. Provide a copy of your editorial policies and procedures. Also include the names and affiliations of the members of your editorial and/or medical board. 9. The vendor must have policies/procedures in place regarding the quality control of the drug information and associated RXCUI mapping file. Provide these policies/procedures in your response. 10. Include 5 English monographs and their Spanish equivalents in both XML format and an example of the final presentation format. 11. Include your DTD. 12. Include a sample of the stand-alone monograph-to-RXCUI mapping file that covers at least 10% of the entire monograph collection being offered, including the 5 example monographs required in #8 above. If the RXCUI mappings will be embedded in the monograph XML, provide those embedded mappings in the 5 example monographs required in #8 above.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/HHS/NIH/OAM/NIHLM2017948MM/listing.html)
 
Record
SN04404013-W 20170217/170215234946-7ad6fe27783b7f269675084fecc567f8 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.