Attachment_1__IT_Requirements_Crosswalk.xlsx
XLSX spreadsheet 31 KB Posted
- Solicitation number
- 17-236-SOL-00020
About this file
IT Requirements to be addressed by each contractor as part of proposal.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Questions_from_Vendors.docx | DOCX document | |
| Combined_Synopsis_Solicitation_final.docx | DOCX document | |
| Attachment_2_Est_Active_Files_by_Facility.pdf | ||
| Price_template.xlsx | XLSX spreadsheet | |
| SOO_3_29_2017_RFP.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
All
| Category | Notional Feature/Functionality | Please indicate if feature or functionailtiy is included in the standard "software package" as "Out of the Box," or if an additional module can be purchased. | Please note if a Minor Enhancement or Major Enhancement is needed. Leave Blank if not offered. |
| General System Requirements | Meet Centers for Medicare and Medicaid Services (CMS), The Joint Commission (TJC), National Committee for Quality Assurance (NCQA), CARF; and Accreditation Association for Ambulatory Health Care (AAAHC) applicable credentialing standards. | ||
| General System Requirements | Integrate with verification systems such as the National Practitioners Data Bank (NPDB), State Licensing Boards, American Board of Medical Specialties (ABMS), American Medical Association (AMA) | ||
| General System Requirements | Allow for electronic exchange of information for verification of licensed or certified health care practitioners requisite skills and expertise to manage and treat patients and to perform the medical procedures that are required to provide the authorized services. Hard: Data in transit and at rest should be encrypted utilizing FIPS 140‐2 as the requirement. | ||
| General System Requirements | Capacity to comply with Section 508 of the Rehabilitation Act of 1973 | ||
| General System Requirements | The system shall store and allow IHS to accept, modify, process, review, and export system case data elements relating to Credentialing Verification | ||
| General System Requirements | The system shall store system case related files from web submitted reports and other IHS and Industry AE IT systems (scans of paper reports, medical records, attachments to electronic submissions, reporter correspondence, etc.). Have capability to upload and store external documents. Add Immunizations, form letters, affiliation requests. | ||
| General System Requirements | The system shall allow the user to store system case data from various sources and follow‐up submissions. The system shall allow for the convenient review of case data at the source level and a case level aggregation of all source reports. System should have the ability to create role based access. When is the user authorized to create or access an account and what volume of user data is expected per standard user? IT Requirement for access to data by user? Username and password customization. | ||
| General System Requirements | The system shall house a dictionary of system regulated characteristics, such as providers and names for report data standardization. | ||
| General System Requirements | The system shall store dates in case records for evaluating regulatory compliance, records management performance metrics, case review milestones, and correspondence tracking. (NARA Regulatory Requirements).Ability to mark specific data for alerts, monitoring, and reporting. (i.e. 6 months prior to expiration date) | ||
| General System Requirements | The system shall allow the user to configure notifications to applicants, administrator, reviewers emails based on predefined criteria | ||
| General System Requirements | The system shall provide correspondence management functionality, paper and electronic based (correspondence IHStory, letter generator for submission acknowledgement, etc.) | ||
| General System Requirements | The system shall create new case records from Application Platform submissions | ||
| General System Requirements | The system shall be able to exportfiles from report data. Standard export formats such as PDF, XLS, and CVS | ||
| General System Requirements | The system shall disable user accounts, not DELETE User Accounts, according to existing IHS access policies. Required IT Technical Requirement | ||
| General System Requirements | The system shall provide a time out function for user inactivity according to IHS policies. | ||
| System Security Requirements | Comply with the Federal Information Security Management Act (FISMA) 2002 including the National Institute of Standards and Technology (NIST) Special Publication (SP) 800 Series and associated Federal Information Processing Standard Publications (FIPSPUB) standards to meet security control baselines supporting data in accordance with FIPS 199. Hard: Part of this compliance is receiving an ATO and developing all system documentation. | ||
| System Security Requirements | The system shall support integration with Microsoft Active Directory using LDAP. | ||
| System Security Requirements | The system shall authenticate internal users with IHS's Single Sign‐On (SSO) | ||
| System Security Requirements | The system shall support two factor authentication using Federal HSPD-12 approved PIV Cards. | ||
| System Security Requirements | Comply with the Federal Information Security ‐ Health Insurance Portability and Accountability Act privacy requirements HIPAA | ||
| System Security Requirements | The website should be HTTPS based and it should meet the minimum SSL requirements. | ||
| Public Facing | The system shall allow the applicant to submit via modern web browsers, mobile and desktop systems. | ||
| Public Facing | The system shall allow the applicant to create an account (including name, email address, etc.) IT Requirement: Account to be created by System Administrator/SME and NIH 7.1.3 The system shall give the user the ability to save or change password. | ||
| Public Facing | The system shall allow the applicant to update account information as needed | ||
| Public Facing | The system shall allow the applicant to login to their accounts using verified credentials (email/password,etc.). NIH 7.1.2 The system shall allow the user to log into the credentialing application using their login id and password, provided he/she is a n authorized user. | ||
| Public Facing | The system shall provide UI controls to use mobile device camera hardware to take pictures of application support materials | ||
| Public Facing | The system must provide UI controls that autocomplete fields with known lists of values. The system should be designed to use pre-defined standard criteria drop-down lists. | ||
| Public Facing | The system shall allow intuitive UI controls for the Applicants to browse and make selections. | ||
| Public Facing | The system shall allow the Applicant to upload additional items (pictures, pdfs, etc.) | ||
| Public Facing | The system shall allow the Applicant to create a follow up documents to provide updated or new information. The system shall provide for versioning control for all uploaded documents. | ||
| Public Facing | The system shall allow the Applicant to view and save a draft report | ||
| Public Facing | The system shall allow the Applicant to view draft and submitted documents | ||
| Public Facing | The system shall ask the Applicant to read and accept or reject the Terms and Conditions | ||
| Public Facing | The system shall send a notification to the IHS administrator confirming account profile setup | ||
| Public Facing | The system shall send notification to Applicants confirming document submission, including a Application identifier for correspondence with IHS | ||
| Public Facing | The system shall allow the Administrator to manage submitter accounts (i.e. password reset and other administrative items). The system shall support applicant self service password reset or integration with existing solutions within IHS (i.e. Self Service Password Reset (SSPR) | ||
| Public Facing | The system shall support Active Directory security group permissions and the ability to assign business roles based upon business function. | ||
| Public Facing | The system shall allow the Applicant to create a new system application and displaying prompts appropriate for that context. | ||
| Business Administration | The system shall track business metrics for the case management workflow (case load for records management users, time taken for major workflow steps, etc.) | ||
| Business Administration | The system shall allow read‐only users to view case information (i.e. case summary, case information, review, etc.) | ||
| Business Administration | The system shall allow the assignment of roles based permissions and functions | ||
| Business Administration | The vendor shall perform cleanup of legacy data necessary to migrate case records to system COTS. What is the level of data migration required between the legacy applications and the new application? This should be part of the statement of work. | ||
| Business Administration | The system shall migrate case data from the legacy systems to IHS system. | ||
| Business Administration | The vendor shall provide user training for xx users, across the user roles expected to be needed by IHS | ||
| Business Administration | The system shall allow the user to track and monitor each case throughout the workflow | ||
| Records Mgt & Workflow | The system shall adhere to best practices in User Interface design to minimize data entry effort (minimize number of clicks or steps required to enter AE and PC data, support tabbing, etc.) | ||
| Records Mgt & Workflow | The system shall determine whether the new data belongs to an existing case to prevent duplicate cases from being created and to keep all reports about one event together | ||
| Records Mgt & Workflow | The system shall provide User Interface controls for users to search for duplicates and to manually merge cases when cases regarding the same application are discovered | ||
| Records Mgt & Workflow | The system shall allow System Administrator to manually create new cases | ||
| Records Mgt & Workflow | The system shall allow the user to scan paper submissions using Optical Character Recognition configured to minimize time by adding page numbers, case identifiers, and other data to document scans. | ||
| Records Mgt & Workflow | The system shall hold contact information for other regulatory organizations, and be able to send reports not applicable to CFSAN to the correct organization | ||
| Records Mgt & Workflow | The system shall auto‐code case data to standardize categories and their associated information (xxxx, etc.) | ||
| Records Mgt & Workflow | The system shall provide User Interfaces for verifying the auto‐codings done by the system for case records created from electronic data sources | ||
| Records Mgt & Workflow | The system shall provide User Interfaces to allow the management of case related files (scans of paper reports, medical records, attachments to electronic submissions, reporter correspondence, etc.) | ||
| Records Mgt & Workflow | The system shall allow the population of all data (relating to the applicant) at the report and case level, where appropriate. | ||
| Records Mgt & Workflow | The system shall allow the User to manually associate data from dictionaries | ||
| Records Mgt & Workflow | The system shall allow the user to manually associate system codes with a report | ||
| Records Mgt & Workflow | The system shall provide the User UI controls that autocomplete all data entry fields for which list of values are known ( names, medical terms, etc.) | ||
| Records Mgt & Workflow | The system shall provide functionality for records management user to QA a created or updated case before being made available for review workflow | ||
| Records Mgt & Workflow | The system shall allow the assignment of cases and reports to records management users, for data entry, auto‐code verification, and other records management functions, from all sources. | ||
| Records Mgt & Workflow | The system shall provide UI controls for reviewers to add comments and conclusions to a case from a reviewer perspective | ||
| Records Mgt & Workflow | The system shall provide the ability to build semi‐structured workflows where the user chooses the next task from a menu of options. | ||
| Records Mgt & Workflow | The system shall provide the ability to build fixed‐sequence workflows where the order of tasks is predetermined. | ||
| Records Mgt & Workflow | The system shall provide the ability to design workflows in which a sequence of tasks is altered in a defined manner based on defined business rules. | ||
| Records Mgt & Workflow | The system shall provide the ability for any step in a workflow to be re‐routed or placed on hold if no authorized user is available to perform the next step in the workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability for Business Units (BUs) to define and associate a case status identifier ‐ such as Created, Assigned, In Process, Reviewed, Approved, Complete, and Cancelled ‐ with any task in a workflow. | ||
| Records Mgt & Workflow | The system shall require that changes to case status identifier definitions be approved by an authorized role or user. | ||
| Records Mgt & Workflow | The system shall provide the ability to trigger automated or manual events based on changes in case status. | ||
| Records Mgt & Workflow | The system shall provide the ability for Business Units to define what roles can assign each status in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to establish a routing list for a workflow by assigning roles to tasks. | ||
| Records Mgt & Workflow | The system shall provide the ability for a workflow to have multiple role to task mappings associated with it. | ||
| Records Mgt & Workflow | The system shall provide the ability for each step in a workflow to be automatically assigned to or routed to any user designated to work on the case based on userid or role. | ||
| Records Mgt & Workflow | The system shall provide the ability for each step in a workflow to be automatically assigned to or routed to any user authorized to work on the case by editing the routing list established for the workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability for workflow authors to specify contextual help for any task in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to customize all workflows based on graphical configuration tools that do not require programming. | ||
| Records Mgt & Workflow | The system shall provide configuration management and version control capabilities for workflow definitions. | ||
| Records Mgt & Workflow | The system shall provide the ability to display the status of all tasks in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to display both the completed and incomplete tasks in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to take some action on steps in a workflow. | ||
| Records Mgt & Workflow | The system shall automatically present the next task to the appropriate user or software service when a form or task is completed. | ||
| Records Mgt & Workflow | The system shall provide the ability to route the completed form or task to the next person, role, or activity in the workflow for the next processing step. | ||
| Records Mgt & Workflow | The system shall allow a user to select any incomplete task to perform next in a semi‐structured workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to close a case that uses a semi‐structured workflow after all required tasks are completed by the case worker. | ||
| Records Mgt & Workflow | The system shall provide the ability to import and export data as a step in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to electronically sign forms in a workflow. | ||
| Records Mgt & Workflow | The system shall provide the ability to record the amount of time spent on a task in a workflow either manually or in an automated manner. | ||
| Records Mgt & Workflow | The system shall provide the ability to capture information about time spent on each task by role, individual, and case. | ||
| Records Mgt & Workflow | The system shall provide the ability to calculate the number of days between any two dates to support processes that have deadlines for performing particular actions. | ||
| Records Mgt & Workflow | The system shall provide the ability for workflow authors to specify workflow events and states that require automated notification. | ||
| Records Mgt & Workflow | The system shall provide the ability for workflow authors to specify to whom notifications are to be sent. | ||
| Records Mgt & Workflow | The system shall send notifications when a trigger condition occurs as defined in the Business Rules. | ||
| Records Mgt & Workflow | The system shall provide the ability to generate notifications based on the amount of time that has expired since a previous event or status change (e.g., time expired since the case was created or the last status was entered). | ||
| Records Mgt & Workflow | The system shall provide the ability to deliver notifications via text messaging, web forms, and email. | ||
| Records Mgt & Workflow | The system shall provide the ability to receive notifications and correspondence via text messaging, web forms, and email ‐ and route them as defined in the business rules. | ||
| Business Rules | The system shall provide the ability to define and execute business rules, and associate them with workflows. | ||
| Business Rules | The system shall provide the ability to define business rules that change workflows dynamically based on the state of the information in the workflow or the role of the user performing a workflow action. | ||
| Business Rules | The system shall provide the ability to perform automated actions such as sending correspondence, sending email, generating reports, and updating case status, when an event triggers a business rule. | ||
| Business Rules | The system shall provide the ability to monitor case events, workflow status, field values, and due date ‐ and trigger automated actions based on those elements. | ||
| Business Rules | The system shall provide the ability to execute business rules that modify the sequence of workflow tasks. | ||
| Business Rules | The system shall provide the ability for business rules to be created, edited, maintained, and applied globally, or by Business Unit. | ||
| Business Rules | The system shall provide the ability to identify dependencies among business rules. | ||
| Business Rules | The system shall keep an audit trail of all changes made to business rules. | ||
| Reporting | The system shall provide the ability to generate reports using any information associated with a case. | ||
| Reporting | The system shall provide the ability to filter and sort report data based on the values contained in any field. | ||
| Reporting | The system shall provide each Business Unit the ability to assign read permissions for its data elements, dashboards, and reports by user and role. | ||
| Reporting | The system shall allow access to unredacted reports containing privacy data to only those users granted access to the privacy data. | ||
| Reporting | The system shall substitute special characters (e.g., asterisks) for any field in a dashboard or report containing a privacy‐protected variable – if the report is requested by a user whose role is not granted access to privacy‐protected data. | ||
| Reporting | The system shall provide the ability to subscribe to specific reports and notifications approved for dissemination by the Business Unit. | ||
| Reporting | The system shall provide the ability to schedule the delivery of reports, and to distribute them to a specified list of recipients. | ||
| Reporting | The system shall provide the ability to schedule notifications, and to distribute them to a specified list of recipients. | ||
| Reporting | The system should provide the ability for a supervisor to click on a report showing cases assigned to IHS subordinates, and open an email that is prepopulated with the email address in the "To" field and the case number in the "Subject" field. | ||
| Reporting | The system shall provide the ability to open and display one or multiple cases by clicking on the report line for the desired cases. | ||
| Reporting | The system shall provide the ability to display trend analysis via scatterplot, line charts, bar charts, and pie charts. | ||
| Reporting | The system should provide the ability to perform statistical calculations like correlations and percentile calculations. | ||
| Reporting | The system shall provide the ability to design and generate canned reports. | ||
| Reporting | The system shall provide the ability to design and generate canned reports using any fields defined in the system. | ||
| Reporting | The system shall provide the ability to design and generate canned reports that filter data based on the values associated with selected fields. | ||
| Reporting | The system shall provide templates for reports that can be customized for IHS's needs. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for all active cases in a Business Unit. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for all active cases assigned to a supervisor or screener. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for all active cases assigned to a user. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for all active cases due within 24 hours. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for all active cases past the due date. | ||
| Reporting | The system shall provide the ability to design and generate canned reports that list cases ordered by due date. | ||
| Reporting | The system shall provide the ability to design and generate canned reports for cases closed in the past week, past month, past quarter, or any other designated time period. | ||
| Reporting | The system shall provide a printable canned report that shows all of the data related to a case from forms, logs, emails, imported files, correspondence, and documents contained in the case folder. | ||
| Reporting | The system shall provide authorized users the ability to design reports without the need to write code or SQL statements. Hard: Does not want users querying SQL directly | ||
| Reporting | The system should provide a "wizard‐driven" report interface for designing and generating ad hoc reports. | ||
| Reporting | The system shall provide the ability to specify report content, format, drill‐down and roll‐up options using a point‐and‐click interface. | ||
| Reporting | The system shall provide the ability to control the sort order of columns on reports. | ||
| Reporting | The system shall provide users in each Business Unit the ability to design and run ad hoc reports using any information in cases for which they have been granted access. | ||
| Reporting | The system shall provide the ability to save the configurations of ad hoc reports for reuse. | ||
| Reporting | The system shall provide the ability to print an unpopulated form, populated form, dashboard, report, correspondence, attached file, or file in a case folder. | ||
| Reporting | The system shall provide the ability to print a case report both to paper and to Microsoft Word and .pdf formats. | ||
| Reporting | The system shall provide the ability to print case reports that are legible, professional in appearance, and usable for an investigation, litigation, official correspondence, or other purposes. | ||
| Reporting | The system shall provide the ability to generate dashboards using any information associated with a case folder. | ||
| Reporting | The system shall provide the ability to design and generate graphical dashboards that report on any group of case data elements (e.g.; case ID, case type, Business Unit, date opened, completion status, electronic signatures received and customer name). | ||
| Reporting | The system shall provide the ability to design and generate graphical dashboards based on the most recent state of the information contained in the system. | ||
| Reporting | The system shall provide the ability to design and generate graphical dashboards whereby the data is filterable and sortable on any data element. | ||
| Reporting | The system shall provide the ability to display dashboards using any information associated with an inactive case such as IHStorical reports, cases closed per month, and weekly staff hours on reference requests. | ||
| Reporting | The system shall provide the ability to design and generate dashboards using any group of data elements specific to a Business Unit. | ||
| Case Administration | The system shall provide the ability to initiate cases. | ||
| Case Administration | The system shall automatically assign a unique ID to each case. | ||
| Case Administration | The system shall provide the ability to automatically generate unique alphanumeric IDs for cases based on business unit identifier or group name, and type of case. | ||
| Case Administration | The system shall provide the ability to manually enter unique alphanumeric IDs for cases. | ||
| Case Administration | The system shall provide the ability for each Business Unit to customize its case types, and process to a decision. | ||
| Case Administration | The system shall provide the ability for each Business Unit to customize workflows for each case type. | ||
| Case Administration | The system shall provide the ability for case initiation forms to be customized based on the needs of each Business Unit. | ||
| Case Administration | The system shall provide the ability for a user or triggering event to initiate a new case by pre‐populating an established form. | ||
| Case Administration | The system shall provide the ability for a user or triggering event to initiate a new case by copying selected data elements from a completed case initiation form. | ||
| Case Administration | The system shall determine if the case proposed in the initiation form is a potential duplicate of an existing case. | ||
| Case Administration | The system shall notify the user assigned to the case if a case being initiated is potentially a duplicate. | ||
| Case Administration | The system shall provide the ability for Business Units to define categories for cases, in a flat or hierarchical structure. | ||
| Case Administration | The system shall allow cases to be associated with one or more categories. | ||
| Case Administration | The system shall provide the ability to assign and manage cases. | ||
| Case Administration | The system shall provide the ability for Business Units to control the assignment of their cases. | ||
| Case Administration | The system shall provide the ability to assign a case to a role. | ||
| Case Administration | The system shall provide the ability to assign a case to a specific user. | ||
| Case Administration | The system shall provide the ability to assign a case to multiple users concurrently. | ||
| Case Administration | The system shall provide the ability to automatically assign cases based on business rules. | ||
| Case Administration | The system shall provide the ability to record both the assigning role and the assignee role as owners of the case. | ||
| Case Administration | The system shall provide the ability for multiple users that are authorized to work on a case to do so concurrently. | ||
| Case Administration | The system shall allow users to open and view multiple cases simultaneously. | ||
| Case Administration | The system shall provide the ability for supervisors or screeners to reassign a case to a different user. | ||
| Case Administration | The system shall provide the ability for supervisors and screeners to specify the priority of each case. | ||
| Case Administration | The system shall provide the ability for supervisors and screeners to specify due dates to each case they assign. | ||
| Case Administration | The system shall provide the ability for an incomplete case to be closed by a role with rights to perform this action. | ||
| Case Administration | The system shall provide the ability for users with appropriate permissions, to change or correct certain fields (e.g., email address, mail address, phone number, etc.) in a closed case. | ||
| Case Administration | The system shall provide the ability to generate an audit log entry for any action performed on a case. | ||
| Case Administration | The system audit log entry shall include the data element that was modified, the role and person who made the change, and the time/date of the change. | ||
| Case Administration | The system shall provide the ability for workflow authors to flag databases, fields, repositories, documents, and correspondence that require privacy protection or other types of protection. | ||
| Forms, Screens, Fields, and Databases | The system shall provide templates for workflow forms. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to define and map fields in forms to a database. | ||
| Forms, Screens, Fields, and Databases | The system shall persist data obtained using forms to a database. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to constrain data in fields to values in a pick list. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to enter data in fields that are not constrained by a pick list (e.g., first name, last name, street address). | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to highlight form field names, form field entries, and report field entries based on specified business rules. | ||
| Forms, Screens, Fields, and Databases | The system shall provide a field on a form for error messages, system announcements, and notifications. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to designate fields on a form as mandatory, by Business Unit. | ||
| Forms, Screens, Fields, and Databases | The system shall display an error message if a mandatory field is not populated. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to populate fields on a form with values entered on a previous form (e.g., customer name) that belong to that same case. | ||
| Forms, Screens, Fields, and Databases | The system shall support one‐to‐many relationships between fields on forms, and persist them to a database accordingly. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to create workflow‐specific forms. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to define a workflow using structured workflow forms that are saved in a database. | ||
| Forms, Screens, Fields, and Databases | The system shall provide forms that can be customized for any step in a workflow. | ||
| Forms, Screens, Fields, and Databases | The system shall provide customizable forms that allow workflow authors to assign a displayable name for each field. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to arrange the position of fields on a form. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to specify the acceptable values for each field on a form. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to validate field entries for any field on a form. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to perform cross‐field validations when the content of one field on a form is constrained by values in a different field on the form. | ||
| Forms, Screens, Fields, and Databases | The system database shall provide the ability to define the types of metadata associated with cases and the rules associated with the management of those metadata elements. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to customize all forms and reports based on graphical user interface (GUI) configuration tools that do not require programming. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to customize forms and menus in terms of screen layout, font, font size, font style (plain, bold, italic, underline) and color. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to save, present, store, and manage fully or partly populated forms for a case. | ||
| Forms, Screens, Fields, and Databases | The system shall provide a graphical user interface (GUI) for accessing all form‐based functionality. | ||
| Forms, Screens, Fields, and Databases | The system GUI shall provide the ability to display pictures and graphic objects like NARA’s logo in GIF, TIFF, or JPEG format. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability for the user to add/modify/update/delete fields to a form . | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability for the user to add fields to a form while working on the form in the context of a workflow. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to cut and paste information from MS Word, MS Excel, Google docs, Google sheets, PDF files, and HTLM forms into a case form or document. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to purge database fields designated as "non‐record" fields when a case is closed. | ||
| Forms, Screens, Fields, and Databases | The system shall provide the ability to designate a database table populated in a workflow as a permanent or temporary record. | ||
| Document Management | The system shall provide a document repository that can establish folders, and store documents and files within them. | ||
| Document Management | The system shall provide a document repository that can manage versions of folders, documents and files. | ||
| Document Management | The system shall provide a document repository that can associate folders, document and files with cases. | ||
| Document Management | The system shall provide a document repository whereby documents and files can be shared based on roles and access permissions. | ||
| Document Management | The system shall provide the ability to check‐out, edit, and check‐in documents and files stored in the document repository. | ||
| Document Management | The system document repository shall provide the ability to create, edit, and control versions of documents that are attached to a case. | ||
| Document Management | The system shall provide the ability to store and access files in any format Electronic Records, in a case folder (e.g.; documents, pictures, audio, video, etc.). Hard: Should limit the format to specific types, converting a file is not difficult and reduces system and application requirements. | ||
| Document Management | The system shall provide the ability to store and access text files in any format specified by IHS. | ||
| Document Management | The system shall provide the ability to store and access image files in Electronic Records (e.g.; TIFF, JPEG, GIF, PNG, etc.). | ||
| Document Management | The system shall provide the ability to store and access Microsoft Office files. | ||
| Document Management | The system shall provide the ability to store and access correspondence in a case folder. | ||
| Document Management | The system shall provide the ability to save/restore/search snapshots of a form at any point in a workflow. | ||
| Document Management | The system shall provide the ability to store and access outgoing correspondence in a case folder. | ||
| Document Management | The system shall provide the ability to store and access incoming correspondence (scanned) in a case folder. | ||
| Document Management | The system shall provide the ability to store snapshots as image files in the document repository. | ||
| Document Management | The system shall provide the ability to create, modify, and control templates for correspondence and email. | ||
| Document Management | The system should provide a spelling and grammar check feature to identify erroneous or non‐standard spelling or grammar, offer alternatives to the user, and allow the user to auto‐correct or ignore/reject editing suggestions. | ||
| Document Management | The system shall provide the ability to edit and customize correspondence, and automatically save it in the case folder when it is sent. | ||
| Document Management | The system shall provide the ability for multiple reviewers to insert comments in a draft document in a manner that identifies the user and Unit making the comment. | ||
| Document Management | The system shall provide the ability to convert a chat into a text file. | ||
| Document Management | The system shall provide the ability to capture text copied and save it in the case folder. | ||
| Collaboration | The system should provide tools for building or integrating with a knowledge base system. | ||
| Collaboration | Allow for the electronic exchange of information among sites, between Areas, and with Headquarters | ||
| Collaboration | The system should provide tools for building Wiki's, Blogs, Bulletin Boards, and Discussion Groups. | ||
| Collaboration | The system should provide tools for integrating with Wiki's, Blogs, Bulletin Boards, and Discussion Groups. | ||
| Collaboration | The system shall provide a Provider portal accessible via the Internet. | ||
| Collaboration | The system portal shall provide a navigation wizard that allows users to answer questions about their interests, and then provide links to the resources that address those interests. | ||
| Collaboration | The system portal shall enable an authorized user to access the status of their cases based on a system provided case ID. | ||
| Collaboration | The system shall provide the ability to publish documents for applicant or agency‐wide access via an HTML link. | ||
| Collaboration | The system shall provide the ability to display FAQs, Business Unit policies, procedures, documentation, and contact lists; and provide navigation links to those resources. | ||
| Collaboration | The system should provide web chat capabilities. | ||
| Collaboration | The system shall provide web accessible training materials. | ||
| Roles and Access Controls | The system shall provide the ability to authorize and control access to all information in databases, repositories, documents, and correspondence based on designated roles, user accounts, and permissions. Hard: Role Based Access Control (RBAC) Note:Recommend to assess new IAM solution (ITAC) for integration capabilities and automated provisioning base access. | ||
| Roles and Access Controls | The system shall provide the ability to authorize and control access to all system features and functions based on designated roles, user accounts, and permissions. NIH 7.1.4 The system shall allow different access profiles depending on the user, which will control the information they have access to and what they can edit. | ||
| Roles and Access Controls | The system shall provide the ability for Business Units to establish roles to manage the create, read, update, and delete permissions for information in their databases, repositories, documents, and correspondence. | ||
| Roles and Access Controls | The system shall provide each Business Unit the ability to associate users with user accounts and roles. | ||
| Roles and Access Controls | The system shall provide the ability to associate access permissions for database fields, business rules, documents, and correspondence with user accounts or roles. | ||
| Roles and Access Controls | The system shall provide the ability to define a hierarchy of roles whereby designated role can be subordinate to another regarding access permissions to data or system function (e.g.; supervisor and staff). | ||
| Roles and Access Controls | The system shall provide the ability to define a hierarchy of roles by Business Unit or across multiple Business Units. | ||
| Roles and Access Controls | The system shall provide the ability to establish supervisor roles that can define subordinate roles for a Business Unit, or multiple Business Units. | ||
| Roles and Access Controls | The system shall provide the ability for a supervisor role to define user accounts and associate access permissions with those accounts. | ||
| Roles and Access Controls | The system shall provide the ability to establish a workflow author role that can define, design, implement, and change workflows and associated business rules. | ||
| Roles and Access Controls | The system shall provide the ability to define the access permissions for workflow designer roles by Unit or for multiple Business Units. | ||
| Roles and Access Controls | The system shall provide a Business Unit with the ability to add, change and delete roles associated with each of its workflows and the steps that comprise them. Hard: Needs a robust log generating capability. | ||
| Roles and Access Controls | The system shall provide the ability for a Business Unit to associate a user with different roles in different workflows. | ||
| Roles and Access Controls | The system shall provide the ability for users to be associated with multiple roles in the same workflow. | ||
| Roles and Access Controls | The system shall provide the ability to define the roles required to manage cases, and associate roles to case management functions. | ||
| Roles and Access Controls | The system shall allow users associated with case management roles to access all workflows associated with their cases. | ||
| Roles and Access Controls | The system shall provide the ability to define and enforce permissions for reading and updating fields on forms. | ||
| Roles and Access Controls | The system shall provide the ability to define and enforce create, read, update, and delete permissions at the file level for all files. | ||
| Roles and Access Controls | The system shall provide the ability for a user, assigned to an authorized business role, to manage read/write permissions on information associated with that unit's cases. | ||
| Roles and Access Controls | The system shall allow only users associated with the workflow author role to create or edit workflows. | ||
| Roles and Access Controls | The system shall limit the ability to delete cases and associated information to specifically authorized users or roles. | ||
| Roles and Access Controls | The system shall ensure that when an item falls under a records schedule, no records contained in the system are deleted except in accordance with an approved disposition authority in a IHS. | ||
| Profiles | The system shall allow the Organization Profile to include a field for the organization name. | ||
| Profiles | The system shall allow designation of primary and secondary points‐of‐contact for an Organization. | ||
| Profiles | The system shall allow creation of notes in Organization Profiles. | ||
| Profiles | The system shall allow for a hierarchy or link between Organizations (e.g. sub‐groups and departments). | ||
| Profiles | The system shall provide the ability for each system user to be associated with a User Profile. | ||
| Profiles | The system shall allow the User Profile to include fields such as phone numbers, email address, division/branch, job title, office location, and mailing address for the user. | ||
| Profiles | The system shall provide the ability for notes or optional fields to be added to user profiles. | ||
| Profiles | The system shall provide the ability to set up lists that define names and structures for organizations, positions, facilities and places associated with cases. | ||
| Data Import/Export | The system shall provide the ability to perform bulk data imports and exports using USB and eSATA devices. Hard: Will the agency be providing and managing the external devices? BYOD has not been established for IHS. Allowing bulk data export also presents the opportunity for abuse with large amounts of PII (remember the VA laptop?). | ||
| Data Import/Export | The system shall provide the ability to export data in PDF format, MS Excel format, and comma‐ separated‐values (CSV) format. | ||
| Data Import/Export | The system shall provide the ability to import and export image data files in TIFF, JPEG, GIF and PNG formats. | ||
| Data Import/Export | The system shall provide the ability to import files from SharePoint, Google Drive other IHS required sources | ||
| Data Import/Export | The system shall provide the ability to import data from structured databases. | ||
| Data Import/Export | The system shall provide tools to facilitate the bulk loading of files into database tables. | ||
| Data Import/Export | The system shall provide the ability to export structured data sets | ||
| Mobile | The system shall be accessible to and support interaction with Android and IOS tablets. | ||
| Mobile | The system shall provide tools for developing applications running on Android and IOS mobile devices. | ||
| Mobile | The system shall provide tools and utilities that resize content and forms displayed on large screens to smartphone and tablet screens. | ||
| Mobile | The system shall support two‐way message communications between a mobile device and the system application. | ||
| Mobile | The system should provide tools to build applications that offer the equivalent visual and functional experience whether operated from a tablet, a smartphone, or a desktop. | ||
| Mobile | The system shall be accessible to and support interaction with Android and IOS smartphones. Hard: GFE only. Personally owned equipment should not be allowed. | ||
| Account Management | The system shall provide standardized, web‐based system administration and management tools, accessible to IHS to remotely and securely manage all service provisioning. Hard: If externally facing or off‐premise, many additional security requirements will be required. | ||
| Account Management | The system shall provide the ability for IHS to establish system administrator roles for the provisioning and management of system functions in the IHS master account and associated sub‐accounts. | ||
| Account Management | The system shall implement security controls that authenticate and grant access to account management functions and capabilities only to authorized users. | ||
| Integration | The system shall provide a set of Application Programming Interfaces (APIs) that can be used to develop custom interfaces to other information systems. | ||
| Integration | The system shall provide support for the ODBC (open Database Connectivity) and JDBC (Java Data Base Connectivity) APIs. | ||
| Integration | The system shall provide the ability to invoke and interact with message‐based interfaces using web services, and REST APIs. | ||
| Integration | The system shall provide the ability to paste information from the Windows clipboard into fields in the system. | ||
| Integration | The system shall be accessible from standard IHS workstations via a IHS supported web‐browsers (i.e. MS Internet Explorer v11, Google Chrome v51.x, Mozilla Firefox v45.x, Apple iOS 9.x, and Google Android | ||
| 5.x mobile operating system. Subject to change) using HTML and HTTPS without the need to install and manage specialized plugins or other client software on the workstation. Must be able to support HTTPS. | |||
| Records Management | Enable facilities manage electronic records of comprehensive provider credentials data such as licensure, board certification, continuing medical education, DEA, other certifications, personal information, education, malpractice information and past claim IHStory, etc. | ||
| Records Management | The system shall provide the ability to enforce record schedule (RS) dispositions for records managed in a case workflow. | ||
| Records Management | The system shall provide the ability to protect closed cases and documents identified as Permanent (Archival) records from editing and deletion until their confirmed transfer to IHS permanent holdings. | ||
| Records Management | The system shall provide the ability to protect closed cases and documents identified as Temporary records from editing and deletion. | ||
| Records Management | The system shall provide the ability for workflow authors to identify and associate dispositions with any identified records in any format, as well as their controlling Records Schedule. | ||
| Records Management | The system shall provide the ability for all cases and associated information identified as records to be indexed, categorized, arranged, and searched by those granted appropriate role‐based access. | ||
| Records Management | The system shall provide the ability for all cases and associated information identified as permanent records to be transferred / exported from the system to holdings in accordance with Metadata Guidance for the Transfer of Permanent Electronic Records and IHS Guidance for the Transfer of Permanent Electronic Records. | ||
| Records Management | The system shall provide the ability to send alerts when records (Temporary and Permanent) are eligible for disposition. | ||
| Records Management | The system shall provide the ability to track and log when, what, and by whom information is changed or deleted for cases and any associated information identified as records. | ||
| Records Management | The system shall provide the ability to clearly identify cases and any associated information identified as records by organization or function for reporting, tracking, search, transfer, or disposition purposes. | ||
| Records Management | The system shall provide the ability to generate reports and dashboards for records management purposes. | ||
| Records Management | The system shall provide the ability to preserve long term and Permanent cases, records, and their associated metadata in formats that comply with IHS guidance. | ||
| Records Management | The system shall provide the ability to perform legal and other holds on Permanent cases, records, and their associated metadata. | ||
| Records Management | The system shall provide the ability to design workflows such that records management functions are performed in an automated manner without requiring direct user involvement. | ||
| Records Management | The system shall provide the ability to delete Temporary records, and transfer/export Permanent records. Hard: The system should have a robust log generating functionality. If someone deletes a temporary record, we should be able to determine the actor. | ||
| Search | The system shall provide the ability for users to search for information in case databases built from form inputs, metadata about database items, and database schema. | ||
| Search | The system shall provide the ability for users to search for information in case attachments, files imported to cases, files created in the repository, case correspondence, and reports. | ||
| Search | The system shall provide the ability to perform full text searches of documents in a case folder. | ||
| Workflow | The system shall display status of where the provider is in the approval process. (pending, approved) | ||
| Workflow | The system shall be able to determine requirements specific to Medical Staff Categories; which include Provisional, Active, Temporary, Consultant, Courtesy, Associate, or Locum Tenens | ||
| Workflow | The system shall notify user of expiring or expired credentials. | ||
| General System Requirements | The system shall provide a set of Application Programming Interfaces (APIs) that can be used to develop custom interfaces to other information systems, such as National Practitioner Data Bank, Healthcare Integrity and Protection Data Bank, American Medical Association (AMA), The Joint Commission, CARF, and AAAHC. | ||
| Workflow | The system shall allow for the assignment of Emergency privileges. |
Attachment 1: IHS Enterprise Credentialing System Draft IT Requirements
&P/&N
File details come from the government source that posted it. Updated .