Attachment 5 Required Usage Data Statistics with Counter 5 Report Types and Application System Accessibility Requirements_FINAL.pdf

Attachment 5 - Required Usage Data & Statistics with Counter 5 Report Types and Application System Accessibility Requirements

Reporting Requirements for Usage Data and Statistics

1. The Contractor shall provide End-User device usage data and statistics per the PWS Requirements.

2. The Contractor and its associated subcontractors and suppliers (If applicable) shall have the capability to accept and manage up to 2.5

Million Internet Protocol (IP) address. They shall have the documented ability to support the Military Health System (MHS) operational networking environment and multiple physical sites within this environment who access content electronically via the requirements of the

PWS.

3. Usage data and statistics shall be provide base upon Government supplied IP address location data and shall be grouped when possible to indicate a specific sites associate with site or location specific IP address, i.e. if a site is known to be associate with a specific IP address or range or a proxy IP address the reporting shall be consolidate for the site.

4. The Contractor and its associated subcontractors and suppliers (If applicable) shall support usage data and statistic reporting via access other standard library access methods and tools including commercial off the shelf (COTS) single sign on application currently in use by the MHS including but not limited to OpenAthens, EZproxy and others as required.

5. Reporting Format Requirements for Usage Data and Statistics The Contractor shall provide usage data and statistics per the PWS requirements.

6. Usage data and statistics shall be provided to the Government in Counter (Counting Online Usage of Networked Electronic Resources) Release 5, the minimum acceptable Counter Release level shall be Counter 5 format.

6.1 The Contractor shall provide the designated program office or the Government POC via the COR a list of all line item content being supplied or supported under this effort and shall certify Counter 5 compliance and/or capability for each line item of content. If a line item is not Counter 5 compliance or capable or cannot be made Counter 5 compliance or capable the contractor shall submit document reasoning why the item should be exempt from this requirement. The Contractor shall submit a proposed Usage data and statistics reporting structure that meets the government’s requirements. The Government, to include the COR and the Contracting Officer, and Contractor shall work together to come to a mutual agreement. The Government shall have 30 calendar days to respond after official receipt.

If the Government decision is that, a line item shall be Counter 5 compliance or capable the contractor shall have a minimum of 10 months to accomplish the required changes or they may be subject to monetary or other penalties up to 25% of the total contract line item value.

The Contractor shall provide status reporting for all items that have been deemed Counter 5 Compliance Mandatory and for all items that have had approved alternate reporting structure approved. If an Item that has had an alternate reporting structures approved and the contractor has an update or major new release or new version the contractor shall notify the government via the COR regarding its Counter 5 compliance status for all non-compliant items.

The status report shall include all:

• Content Line Item Description

• Plan of action/timeline for Compliance

6.2 Require Counter 5 shall include all standard and optional reports appropriate to the content being delivered by the contractor at a minimum shall provide the standard reports included in Attachment 5 - Counter 5 Report Types and shall provide data per the following requirements.

• The system shall provide the ability to track and report usage down to specific IP address level (based upon Government IP architecture).

• The system shall provide the ability to track and report usage down to the specific user level when access is via IP (based upon

Government IP architecture).

• The system shall provide the ability to track and report usage down to the specific user level when access is via personal accounts.

• The system shall provide the ability to produce standardized and custom reports.

o Standardized Reports shall include:

Total Usage for all provided content by content type, content name, usage location, total numbers of access and turn-away Reports shall also include by content type, content name, usage location all content that is downloaded in PDF format The following usage statistical reports will be available for all components (if applicable):

• Monthly Database Searches & Sessions Requests

• Monthly Database Turnaways

• Total Searches and Sessions by Month & Service

• Monthly Database Usage

• Monthly Full Text Requests

• Monthly Journal Turnaways

• Monthly Journal Usage

• Monthly Journal Usage by Article Type

• Peak Usage

• Monthly User License Statistics

• Monthly Top Search Activity

• Monthly Search/Session Usage

• Monthly Top Linking Activity

Monthly Metrics and Reports: The contractor shall provide the ability to produce standardized reports and metrics in the specified Counter format per the PWS.

Standardized Reports shall include:

• Total Usage for all provide content by content type, content name, usage location, total numbers of access and turn-away o Reports shall also include by content type, content name, and usage location all content that is downloaded in PDF format (if applicable)

The following usage statistical reports will be available for all components:

Monthly Database Searches & Sessions Requests Monthly Journal Usage by Article Type Monthly Database Turnaways Peak Usage Total Searches and Sessions by Month & Service Monthly User License Statistics Monthly Database Usage Monthly Top Search Activity Monthly Full Text Requests Monthly Search/Session Usage Monthly Journal Turnaways Monthly Top Linking Activity Monthly Journal Usage

Counter 5 Report Types

Report Description Comments Book Report 1 Number of Successful Title Requests by Month and Title Book Report 2 Number of Successful Section Requests by Month and

Title

Book Report 3 Access Denied to Content Items by Month, Title and Category

Book Report 4 Access Denied to Content items by Month, Platform and Category

Book Report 5 Total Searches by Month and Title Database Report 1 Total Searches, Result Clicks and Record Views by

Month and Database

Database Report 2 Access Denied by Month, Database and Category Journal Report 1 Number of Successful Full-Text Article Requests by

Month and Journal

Journal Report 1 GOA Number of Successful Gold Open Access Full- Text Article Requests by Month and Journal

Journal Report 2 Access Denied to Full-Text Articles by Month, Journal and Category

Journal Report 5 Number of Successful Full-Text Article Requests by Year-of-Publication (YOP) and Journal

Report Description Comments Multimedia Report 1 Number of Successful Full Multimedia Content Unit

Requests by Month and Collection

Platform Report 1 (formerly Database Report 3)

Total Searches, Result Clicks and Record Views by Month and Platform

Book Report 7 Number of Successful Unique Title Requests by Month and Title in a Session https://www.projectcounter.org/wp-content/uploads/2016/02/APPL.pdf

Journal Report 1a Number of Successful Full-Text Article Requests from an Archive by Month and Journal https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Journal Report 3 Number of Successful Item Requests by Month, Journal and Page-type https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Journal Report 3 Mobile Number of Successful Item Requests by Month, Journal and Page-type for usage on a mobile device https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Journal Report 4 Total Searches Run By Month and Collection https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Multimedia Report 2 Number of Successful Full Multimedia Content Unit Requests by Month, Collection and Item Type https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Title Report 1 (formerly Journal/Book Report 1)

Number of Successful Requests for Journal Full-Text Articles and Book Sections by Month and Title https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Title Report 1 Mobile Number of Successful Requests for Journal Full-Text Articles and Book Sections by Month and Title (formatted for normal browsers/delivered to mobile devices AND formatted for mobile devices/delivered to mobile devices https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Title Report 2 Access Denied to Full-Text Items by Month, Title and Category https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Title Report 3 Number of Successful Item Requests by Month, Title and Page Type https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Title Report 3 Mobile Number of Successful Item Requests by Month, Title and Page Type (formatted for normal browsers/delivered to mobile devices AND formatted for mobile devices/delivered to mobile devices https://www.projectcounter.org/wp-content/uploads/2016/02/APPH.pdf

Application System Accessibility Requirements

1. The system shall provide the ability to access online clinical reference resources across multiple Government-approved devices (e.g.

Government-approved workstations, mobile devices, etc.).

1.1. Multiple devices can be used for access including Desktops, Laptops, Tablets, Mobile Devices including portable devices for use in low-communication/ no communication environments (Kiosk, Devices (Android) (IOS) and Other operating systems on the Government Approved Products List) (if applicable).

1.2. The system shall provide full access to online clinical reference resources via mobile devices (in accordance with the DOD Unified Capabilities Approved Products List (DOD UC APL) (if applicable).

1.2.1.1. Kiosk, Devices (Android) (IOS) or other operating systems on the Government Approved Products List. The system shall provide the ability to access online clinical reference resources across multiple Government-approved platforms (e.g. Government-approved operating systems).

1.3. The Contractor shall provide COTS solutions that are IPv6 capable. An IPv6 capable system or product shall be capable of receiving, processing, transmitting and forwarding IPv6 packets and/or interfacing with other systems and protocols in a manner similar to that of IPv4.

Specific criteria to be deemed IPv6 capable are, or meet the following:

• Conformance to the DOD Information Technology Standards Registry (DISR) developed DOD IPv6 Standards Profile. Systems being developed, procured, or acquired shall comply with the Global Information Grid Architecture and DISR standard IPv6 Capable definition. An IPv6 Capable system must meet the IPv6 base requirements defined in the “DOD IPv6 Standards Profile v2.0” dated August 1, 2007 available from the

DISR.

• Maintenance of interoperability with IPv4. Systems being developed, procured or acquired shall maintain interoperability with IPv4 systems/capabilities. Systems should implement IPv4/IPv6 dual-stack and shall be built to determine which protocol layer to use depending on the destination host it is attempting to communicate with or establish a socket with, if either protocol is possible, systems should employ IPv6.

• Evidence of a migration path and commitment to upgrade all applications and product features to IPv6 (if not currently fully IPv6).

• Availability of vendor/contractor/service provider IPv6 technical support for system implementation and management as needed.

• DOD IPv6 security guidelines, standards, and solutions shall be utilized and adhered to when available.

• Currently, DOD IPv6 Information Assurance (IA) guidance is available from the DOD IPv6 Transition Office (DITO).

1.4 The system shall provide the ability to authenticate authorized users in accordance with the DOD Security standards outlined in Federal Information Processing Standards (FIPS).

1.5 Utilizes Common Access Card (CAC) and Public Key Infrastructure (PKI) technologies to provide the highest level of data security and user authentication Per DOD Guidance.

1.6 The application shall support the existing DOD Single-Sign-On (SSO) capability. Sign-On capability support from existing DOD networks shall be CAC based or username supporting complex password based access login.

1.7 The system shall provide the ability for authorized users to share provided content including clinical reference library content with other authorized DOD users.

Printing

1.8 The system shall provide the ability for authorized users to print information from any Government-approved platform (e.g. a Government-approved operating system).

1.9 The system shall provide the ability for authorized users to print information from any Government-approved platform (e.g. a Government-approved operating system).

Information Sharing & Access Requirements

1.10 The system shall provide the ability for authorized users to share provided content including clinical reference library content with other authorized DOD users.

1.11 Provide and support integration throughout the network via the current and future DOD EHR (Electronic Health Record) portal, to ensure consistent access at the bedside for all health professionals and staff. The vendor/contractor/service provider must provide a single web URL (durable URL) which will provide the Government user with a single point of entry to all resources provided.

1.11.1 The system should provide the ability to operate in a low communications/no communications operational environments (if applicable).

1.11.1.1 The Contractor will be required to work with the Government to support its configuration of devices with the ability to operate in a low communications/no communications environment. This level of effort will include working with the Government to configure the standard core set for the deployed environment; with the understanding that the deployed environment does not require access to all content. Notification will be provide via the COR.

System Accessibility

1.11.2. System downtime shall be minimal and the designated Point of Contact and Contracting Officer’s Representative (COR) shall be notified and shall be provide notification of scheduled maintenance 10-15 calendar days prior to scheduled start date. A minimum of 24 hours before an unplanned system downtime must occur or as soon as a system outage occurs or is noticed.

1.11.2.1 The system shall be accessible 24 hours per day, 7 days a week, per year

1.11.2.2 The vendor/contractor/service provider shall schedule routine maintenance outside of normal clinical hours (in accordance with Government-negotiated time frames and time zones).

System Compatibility and Support

1.12 The product shall be fully compatible with the currently approved web browsers on the Government Approved Product (APL) List including most standard web browsers (Mandatory support required for Legacy Microsoft Internet Explorer for Navy operations, Microsoft Edge. Mozilla Firefox and Google Chrome), which have cookies enabled. To ensure privacy, the product shall use session cookies rather than persistent cookies

1.12.1 The Contractor shall support the current version of all products on the DoD APL and three previous versions back

1.12.2 The product shall be compatible with the Windows operating system environment, Apple operating system environment and other approved operating system environments on the Government APL.

Vendor Content and Portal Support

1.13 All site content and support of the web site is the responsibility of the contractor. This includes technical support to authorized users worldwide.

1.14 The system shall provide the ability to create personal accounts.

2. Online Retrieval Services Capabilities.

2.1 The system shall provide the ability for the authorized user to search by the following search parameters regardless of file extension and/or media type (if applicable):

2.1.1 Search multiple databases simultaneously with hyperlinks to the full-text articles and/or abstracts within the service or product, i.e., user are not linked to an external publishing site.

2.1.2 Removal of duplicate citations (upon request from user) resulting from searching multiple databases simultaneously features the capability of eliminating duplicate citations from search results (if applicable).

2.1.3 Search multiple databases simultaneously with hyperlinks to the full-text articles and/or abstracts within the service or product, i.e., user are not linked to an external publishing site

2.1.4 Removal of duplicate citations (upon request from user) resulting from searching multiple databases simultaneously features the capability of eliminating duplicate citations from search results (if applicable).

2.1.5 Option to select basic or advanced searching interface.

2.1.6 Use of Boolean logic.

2.1.7 Ability to combine search statements.

2.1.8 Search for specific author and the author's institution.

2.1.9 Search for specific journal.

2.1.10 Search for title or specific words in article title or abstract.

2.1.11 Restrict by age, gender, language.

2.1.12 Natural language mapping available for selection by user.

2.1.13 Search by NLM Subject Headings and restrict by NLM subject headings and subheading.

2.1.14 The system shall provide the ability for the authorized user to search by Keyword.

2.1.15 The system shall provide the ability for the authorized user to search by Publication time frame.

2.1.16 The system shall provide the ability for the authorized user to search by Specialty area.

2.1.17 The system shall provide the ability for the authorized user to search by Content type.

2.1.18 The system shall provide the ability for the authorized user to search by taxonomy tags

2.1.19 The system shall provide the ability for the authorized user to search by Media format (Audio, Video, Etc.).

2.2 The system shall provide the ability for authorized user to search content by subject, author, clinical area, or treatment area.

2.2.1 The system shall provide the ability for authorized users to save searches

2.2.2 The system shall provide the ability to filter search results

2.2.3 The system shall provide an auto suggest feature while searching

2.2.4 The system shall provide the ability to sort results based on the search criteria including publication year

2.2.5 The system shall provide the ability to sort results based on the search criteria including publication year

2.2.6 The system shall provide the ability for authorized users to extract information into multiple Government-approved file formats.

2.2.6.1 Example: PPT, XML, XPS, and PDF as directed by the Government; users on Government networks shall have the ability to download PDF articles and book chapters without having to sign-in to or re-sign in to a personal account (if applicable).

2.3 The ability to download complete books chapters from the application in HTML/PDF format (if applicable).

2.3.1.1 The system shall provide the ability to download complete articles/books from the application to support low communication/no communication individual authorized end-user and Government Program office end users and platforms and environments with advanced coordination in PDF Format.

2.3.1.2 The system shall ensure users shall be able to:

2.3.1.2.1 Print/email from within the system citations or, when available, full-text articles.

2.3.1.2.2 Download and email citations or, when available, full-text articles.

2.3.1.2.3 E-mail results of literature search.

2.3.1.2.4 Full-text retrieval results will display or print all graphics (tables, etc.) included in the original content of the print publication.

2.4 The system shall provide Patient Education Handouts with the ability to be tailored for each patient’s specific needs (If applicable).

2.4.1 Patient Education Handouts shall be available at a minimum in both English and Spanish and will support the entire range of medical conditions associated with the supported Medical Specialty and Clinical Areas of Practice. Patient handouts shall include two levels of complexity:

a basic handout and a handout that provides more in-depth information beyond the basics about the specific medical condition.