Attachment E - Traceability Matrix v.4~1.xlsx
XLSX spreadsheet 231 KB Posted
- Attached to
- IDPH Immunization Information System (IIS)
- Solicitation number
- 26-482DPH-OFCDI-B-50619
- Issued by
- Cook County, Illinois
About this file
Summary
This is a Traceability Matrix (Attachment E) for the State of Illinois Department of Public Health Immunization Information System (IIS) Procurement (26-482DPH-OFCDI-B-50619). The solicitation seeks a comprehensive, cloud-based IIS solution to support immunization data management, vaccine inventory tracking, clinical decision support, and reporting for both the Illinois Department of Public Health (IDPH) and the City of Chicago Department of Public Health (CDPH), which operate as two distinct CDC awardees. The solution must be hosted in SOC 2 and Tier III or higher compliant data centers within the United States, be containerized for cloud environments, and support integration with existing Illinois state systems including Health and Family Services/Medicaid, the Illinois Vital Records System, and the Infectious Disease Surveillance System. The system must meet all federal security requirements including HIPAA, FedRAMP Moderate authorization, NIST SP 800-53, and state-specific standards, with comprehensive audit trails, encryption standards, and role-based access controls. The contract requires implementation of a full suite of project management, requirements validation, solution design, data migration, testing, user training, hosting and provisioning, deployment, maintenance and operations, knowledge transfer, and organizational change management services across a defined contract term.
The solicitation mandates compliance with a detailed set of contract requirements, mandatory staffing qualifications, and desirable elements scored across business functionality, technical functionality, and service domains. Key mandatory roles include a Project Manager with minimum three years of project management experience and two years leading similar IIS implementations, a Functional Manager with two years of team leadership experience and one year of IIS implementation experience, a Technical Manager with comparable qualifications, and an Organizational Change Management and Training Manager with two years of state public health experience and one year of IIS implementation experience. Service Level Requirements establish performance standards including 99.9% solution availability, 99.9% application performance for transaction completion, 99.5% data accessibility, critical incident resolution within two hours (95% compliance), high-severity incident resolution within eight hours (95% compliance), disaster recovery restoration within one hour with 15-minute data recovery point objective, and data error rates below 0.5%. Non-compliance with SLRs triggers service credits ranging from 2.5% to 5% of monthly fees depending on the specific metric. The solicitation requires submission of references from three state or local government clients of comparable scope and includes detailed evaluation criteria covering executive summary, offeror background and experience, relevant project experience, proposed staffing approach, and comprehensive responses to functional, technical, and service delivery requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment F - Price Workbook v2~1.xlsx | XLSX spreadsheet | |
| Old State Capitol SHS Scope Concrete Reapirs .docx | DOCX document | |
| GCMS contract ~1.docx | DOCX document | |
| Standard Terms and Conditions ~52.pdf | ||
| C2D Commitment to Diversity Vendor Answer Form.docx | DOCX document | |
| commitment to diversity vendor guidance.pdf | ||
| IIS ipg active registered vendor disclosure form.docx | DOCX document | |
| Blank IIS Vendor Disclosure Form.docx | DOCX document | |
| Fox FY26-27 Elevator Services Contract~2.docx | DOCX document | |
| IIS RFP~1.docx | DOCX document | |
| IIS U-Plan.pdf | ||
| IIS information and technology request for proposal offer to the state of illinois1.pdf |
Show all 12
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
Intro & ToC
| State of Illinois Department of Public Health |
| Immunization Information System Procurement |
| 26-482DPH-OFCDI-B-50619 |
| Attachment E - Traceability Matrix (TM) |
| Information & Instructions | |||
| This workbook serves as the Traceability Matrix, systematically documenting all requirements and desired features for the IIS procurement. Offerors should thoroughly examine each worksheet to grasp the scope, scale, and complexity of this solicitation. Each worksheet provides additional details and information and instructions that must be reviewed and adhered to when preparing your response. Offerors should provide the requested response within the designated cells throughout this workbook, identified with light green shading. | |||
| WORKSHEET TITLE | |||
| Hyperlinked | DESCRIPTION | ||
| F.1. Contract Requirements | This worksheet captures the requirements that will be incorporated into any contract resulting from this solicitation. By submitting an offer in response to this solicitation, the Offeror agrees to comply. Offerors must use the provided drop-down menu to indicate acknowledgement. |
Response required in this worksheet.
F.2. Mandatory Requirements with Evidence This worksheet identifies the Mandatory Requirements, for which all Offerors must provide supporting evidence illustrating their ability to meet them.
Response required in this worksheet.
F.3. Desirable Elements This worksheet identifies the desirable elements IDPH is seeking.
Response required in this worksheet.
Service Level Requirements This worksheet specifies the service level requirements (SLRs) for the contract, detailing minimum performance standards.
No response required in this worksheet.
Performance Definitions This worksheet provides definitions to aid in understanding and compliance of specific service level requirements (SLRs).
No response required in this worksheet.
http://invalid.urihttp://invalid.urihttp://invalid.urihttp://invalid.urihttp://invalid.uri F.1. Contract Requirements
| State of Illinois Department of Public Health |
| Immunization Information System Procurement |
| 26-482DPH-OFCDI-B-50619 |
| Attachment E - Traceability Matrix (TM) |
| Information & Instructions | |||||
| Please carefully review each contract requirement listed below. These requirements shall be incorporated into any contract resulting from this solicitation. By submitting an offer in response to this solicitation, the Offeror agrees to comply with all the contract requirements outlined in this worksheet. In column C, Offerors should indicate acknowledgement by selecting "Agree" from the provided drop-down menu. | |||||
| CONTRACT REQUIREMENTS | Agree Confirmation | ||||
| F.1.1. | The IIS shall maintain compliance with all applicable state and federal regulations, including but not limited to: | Select Your Response | F | 1 | 1 |
| A. IRS Publication 1075: Safeguarding Taxpayer Information, | |||||
| B. HIPAA: Health Insurance Portability and Accountability Act, | |||||
| C. Computer Fraud and Abuse Act of 1986 (as amended in 2010), | |||||
| D. Social Security Number Protection Act of 2010, and | |||||
| E. Current and Future State Security Standards (see Attachment E), and Federal Security Standards, including: | |||||
| i. MARS-E, | |||||
| ii. NIST SP 800-53, | |||||
| iii. FedRAMP Moderate, and | |||||
| iv. Other relevant standards. Refer to DoIT Public Cybersecurity Policies. | |||||
| i. Encryption during all phases of data use (in motion and at rest) in compliance with NIST Publication 800-122, | |||||
| ii. Encryption during all phases of data use (in motion and at rest) in compliance with IRS Publication 1075, | |||||
| iii. Not transmitting or storing any PII using publicly available storage over the internet or any wireless communication device unless the PII is de-identified in accordance with 45 C.F.R § 164.514(b)(2) and encrypted in accordance with applicable laws, and | |||||
| iv. Support encryption for PHI using Advanced Encryption Standard (AES) and open protocols such as TLS, SSL, IPsec, XML encryption, or S/MIME. | |||||
| F.1.2. | The IIS shall be capable of integrating with other State of Illinois systems, including, but not limited to: | Select Your Response | F | 1 | 2 |
| A. Health and Family Services/Medicaid, | |||||
| B. Illinois Vital Records System (IVRS), | |||||
| C. Infectious Disease Surveillance System (IDSS), and | |||||
| D. All other systems as identified by IDPH throughout the contract term. | |||||
| Integration mechanisms must support a variety of approaches, including file-based, API-based, messaging and event-driven architectures, database-level access, middleware and integration platforms, cloud-native services, application-specific connectors, and adherence to industry standards, protocols, and technologies. | |||||
| F.1.3. | The IIS shall include a comprehensive as-built data dictionary that clearly documents the bidirectional mapping and relationship between user interface fields, MuleSoft integration layers, and database fields. This dictionary shall detail each data element’s name, data type, source, allowed values, and dependencies. It must also specify any changes from the initial design to the final implementation, ensuring clarity in data flow and accessibility for system updates and maintenance. | Select Your Response | F | 1 | 3 |
| F.1.4. | IDPH shall retain all ownership rights to data, inputs, and outputs. | Select Your Response | F | 1 | 4 |
| F.1.5. | The IIS shall accommodate diverse populations of users, including those with disabilities and limited English proficiency, as defined in: | Select Your Response | F | 1 | 5 |
| A. Section 504 of the Rehabilitation Act of 1973, and | F | 1 | 6 | ||
| B. Illinois Information Technology Accessibility Act (IITAA) (P.A. 95-307). | F | 1 | 7 | ||
| F.1.6. | The IIS shall comply with recognized usability standards, including: | Select Your Response | F | 1 | 8 |
| A. Americans with Disabilities Act Amendments Act (ADAAA), and | F | 1 | 9 | ||
| B. Older Americans Act, and Rehabilitation Act Section 508 Subpart B Section 1194.21. | F | 1 | 10 | ||
| F.1.7. | The Vendor shall provide DoIT with their most recent Voluntary Product Accessibility Template (VPAT) on an annual basis. Refer to ITI Voluntary Product Accessibility Templates. | Select Your Response | F | 1 | 11 |
| F.1.8. | The IIS shall log activity within the system and forward log information to DoIT’s security incident and event management system (SIEM) | Select Your Response | F | 1 | 12 |
| F.1.9. | The cloud-based hosting platform(s) shall provide a non-shared hosting space for IDPH. | Select Your Response | F | 1 | 13 |
| F.1.10. | The IIS components shall align with IDPH standards and be consistent with the HiTech Act. Interoperability shall leverage Integration Platform as a Service (iPaaS), Service-Oriented Architecture (SOA), and modern web services. | Select Your Response | F | 1 | 14 |
| F.1.11. | All new or updated customer-facing web-based access shall require no desktop software except the IDPH-standard version web browser. | Select Your Response | F | 1 | 15 |
| F.1.12. | Enhancements related to SOA services hosted shall be implemented in Java or .NET. | Select Your Response | F | 1 | 16 |
| F.1.13. | The IIS shall be registered with Cloud Security Alliance (CSA) program. | Select Your Response | F | 1 | 17 |
| F.1.14. | The IIS shall support SAML, OIDCC, OAuth 2.0 support. | Select Your Response | F | 1 | 18 |
| F.1.15. | The software used to install and update the IIS, independent of the mode or method of conveyance, shall be certified free of malevolent software (“malware”). The Vendor shall self-certify compliance with this standard through procedures that make use of commercial malware scanning software. | Select Your Response | F | 1 | 19 |
| F.1.16. | The IIS shall maintain compliance with the Public Health branding standards. | Select Your Response | F | 1 | 20 |
| F.1.17. | Vendor shall meet the Service Level Requirements as defined in Attachment E — Traceability Matrix, worksheet 4. | Select Your Response | F | 1 | 21 |
| F.1.18. | The IIS shall support multiple W3C-compliant browsers, including the latest versions of Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge. | Select Your Response | F | 1 | 22 |
| F.1.19. | The IIS shall be a web-based Solution allowing authorized user access to information 24/7, notwithstanding any pre-agreed upon or emergency maintenance requirements. | Select Your Response | F | 1 | 23 |
| F.1.20. | The IIS and cloud services shall adhere to the (FedRAMP®) approach to security authorizations for Cloud Service Offerings. | Select Your Response | F | 1 | 24 |
| F.1.21. | The IIS shall be continuously hosted in a SOC 2 and Tier III or higher compliant data center in a Vendor maintained Cloud environment, not stored, maintained, or accessed via on-premises servers. All data, including backup data and failover environments, must reside within the United States. | Select Your Response | F | 1 | 25 |
| F.1.22. | The IIS shall support public key/private key encryption and Secure Sockets Layer (SSL) certificates. All communications within the IIS must be protected by at least 256-bit encryption. The IIS must adhere to the principle of "Fail Secure" to ensure that a system in a failed state does not reveal any sensitive information or leave any access controls open for attacks. | Select Your Response | F | 1 | 26 |
| F.1.23. | The Vendor shall support bi-annual, or in the event of a security breach, external audit checks, as well as assist with annual compliance reviews to ensure ongoing adherence to accessibility and security standards. | Select Your Response | F | 1 | 27 |
| F.1.24. | The IIS shall have the ability to access HL7 imports at a solution level. | Select Your Response | F | 1 | 28 |
| F.1.25. | The IIS shall support industry standards and avoid proprietary technologies. | Select Your Response | F | 1 | 29 |
| F.1.30. | The IIS shall be capable of interfacing with the State of Illinois’ identity and access management solution, Okta, via the Security Assertion Markup Language (SAML) or OpenID Connect (OIDC) open standards. | Select Your Response | F | 1 | 30 |
| F.1.31. | The IIS shall maintain an audit trail of database transactions (add, change, delete) identifying the individual performing the transaction, the date and the time of the transaction, and the original data in instances where changes are made. All users shall be able to view the most current data by default. Authorized IDPH personnel shall have the option to view all transactions. | Select Your Response | F | 1 | 31 |
| F.1.32. | The IIS shall be containerized for cloud-based environments. | Select Your Response | F | 1 | 32 |
| F.1.33. | The Solution shall be capable of supporting both IDPH and CDPH while allowing for all data reporting to be conducted separately for each entity as they are two (2) distinct CDC awardees. | Select Your Response | F | 1 | 33 |
| Level 0: Administer System | |||||
| Level 1: Hierarchy Configuration | |||||
| F.1.34. | The IIS shall have the ability to assign role or user permissions by jurisdictional awardee (i.e., IDPH and/or CDPH). | Select Your Response | F | 1 | 34 |
| F.1.35. | The IIS shall have the ability to associate user(s) to a facility. | Select Your Response | F | 1 | 35 |
| F.1.36. | The IIS shall have the ability to associate clinician(s) to a facility. | Select Your Response | F | 1 | 36 |
| F.1.37. | The IIS shall have the ability to associate facility/facilities to an organization. | Select Your Response | F | 1 | 37 |
| F.1.38. | The IIS shall have the ability to establish geographic jurisdictional hierarchy. | Select Your Response | F | 1 | 38 |
| F.1.39. | The IIS shall have the ability to aggregate data across user-defined hierarchies. | Select Your Response | F | 1 | 39 |
| F.1.40. | The IIS shall have the ability to maintain inventory availability in IIS visible to authorized users. | Select Your Response | F | 1 | 40 |
| F.1.41. | The IIS shall have the scalability to add in new vaccine programs (e.g., Vaccines for Children, Pandemic COVID-19 Vaccine Program, Bridge COVID-19 Vaccine Program, etc.) in the future. | Select Your Response | F | 1 | 41 |
| F.1.42. | The IIS shall be capable of supporting Child Vaccine Programs and Adult Vaccine Programs. | Select Your Response | F | 1 | 42 |
| Level 1: System Configuration | 1 | ||||
| F.1.43. | The IIS shall have the ability for jurisdictional admin to maintain separate (Vaccine for Children) VFC supplied inventory in the IIS. | Select Your Response | F | 1 | 43 |
| F.1.44. | The IIS shall have the ability for jurisdictional admin to maintain separate jurisdiction supplied inventory. | Select Your Response | F | 1 | 44 |
| F.1.45. | The IIS shall have the ability for jurisdictional admin to maintain separate private stock inventory. | Select Your Response | F | 1 | 45 |
| F.1.46. | The IIS shall have the ability for jurisdictional admin to manage code sets. | Select Your Response | F | 1 | 46 |
| F.1.47. | The IIS shall have the ability for jurisdictional admin to update National Drug Code (NDC) codes. | Select Your Response | F | 1 | 47 |
| F.1.48. | The IIS shall have the ability for jurisdictional admin to update Vaccine Administered (CVX) codes. | Select Your Response | F | 1 | 48 |
| F.1.49. | The IIS shall have the ability to configure default values to minimize Manufacturers of Vaccines (MVX) codes. | Select Your Response | F | 1 | 49 |
| F.1.50. | The IIS shall have the ability to configure default values to minimize data input. | Select Your Response | F | 1 | 50 |
| F.1.51. | The IIS shall have the ability to display an error message in the user interface when minimum information required is not complete. | Select Your Response | F | 1 | 51 |
| F.1.52. | The IIS shall have the ability to standardize addresses per United States (US) Postal conventions and codes. | Select Your Response | F | 1 | 52 |
| F.1.53. | The IIS shall have the ability to verify validity of addresses (as valid USPS addresses) in the IIS through electronic means (e.g., SmartyStreets). | Select Your Response | F | 1 | 53 |
| F.1.54. | The IIS shall have the ability to geocode addresses. | Select Your Response | F | 1 | 54 |
| F.1.55. | The IIS shall have the ability for jurisdictional admin to modify facility types according to immunization program descriptions and CDC VFC Program descriptions. | Select Your Response | F | 1 | 55 |
| F.1.56. | The IIS shall have the ability to jurisdictional admin to configure rules governing data validation of incoming HL7 messages. | Select Your Response | F | 1 | 56 |
| F.1.57. | The IIS shall have the ability to configure an authorizations agreement as per jurisdictional policy. | Select Your Response | F | 1 | 57 |
| F.1.58. | The IIS shall have the ability to configure a user agreement as per jurisdictional policy. | Select Your Response | F | 1 | 58 |
| F.1.59. | The IIS shall have the ability for display age in year/month/day format in all age display fields (e.g., 2 years, 4 months, 3 days). | Select Your Response | F | 1 | 59 |
| F.1.60. | The IIS shall have the ability to configure the organization group indicators. | Select Your Response | F | 1 | 60 |
| F.1.61. | The IIS shall support rules-based logic to suggest approval or rejection of enrollment form based on review of group indicators. | Select Your Response | F | 1 | 61 |
| F.1.62. | The IIS shall have the ability for jurisdictional admin to manage business rules related to data quality. | Select Your Response | F | 1 | 62 |
| F.1.63. | The IIS shall have the ability for jurisdictional admin to specify business rules for monitoring data quality. | Select Your Response | F | 1 | 63 |
| F.1.64. | The IIS shall have the ability for jurisdictional admin to modify business rules for monitoring data quality. | Select Your Response | F | 1 | 64 |
| F.1.65. | The IIS shall have the ability to configure the organization enrollment form. | Select Your Response | F | 1 | 65 |
| F.1.66. | The IIS shall have the ability to support rules-based logic to suggest approval or rejection of enrollment form based on review of completed fields. | Select Your Response | F | 1 | 66 |
| F.1.67. | The IIS shall have the ability to manage rules-based logic for approval or rejection of enrollment form. | Select Your Response | F | 1 | 67 |
| F.1.68. | The IIS shall have the ability for jurisdictional admin to create enrollment forms based on program requirements. | Select Your Response | F | 1 | 68 |
| F.1.69. | The IIS shall have the ability for jurisdictional admin to modify an enrollment form. | Select Your Response | F | 1 | 69 |
| F.1.70. | The IIS shall have the ability for jurisdictional admin to configure vaccine forecasting business rules. | Select Your Response | F | 1 | 70 |
| F.1.71. | The IIS shall have the ability to apply effective dates and vaccine rules. | Select Your Response | F | 1 | 71 |
| F.1.72. | The IIS shall have the ability to incorporate new vaccines per Advisory Committee on Immunization Practices (ACIP) into the forecasting algorithm. | Select Your Response | F | 1 | 72 |
| F.1.73. | The IIS shall have the ability to support a record search algorithm to return "best matches." | Select Your Response | F | 1 | 73 |
| F.1.74. | The IIS shall have the ability for jurisdictional admin to configure the number of search results to be displayed per jurisdictional policy. | Select Your Response | F | 1 | 74 |
| F.1.75. | The IIS shall have the ability for jurisdictional admin to modify required parameters for patient searches. | Select Your Response | F | 1 | 75 |
| F.1.76. | The IIS shall have the ability for restrict certain data from being included in reports such as sensitive demographic information (e.g., address, phone number, mother's maiden name, Medicaid ID). | Select Your Response | F | 1 | 76 |
| F.1.77. | The IIS shall have the ability for real-time monitoring, reporting, and tracking of data quality issues. | Select Your Response | F | 1 | 77 |
| F.1.78. | The IIS shall be user-friendly and intuitive for all types of users. | Select Your Response | F | 1 | 78 |
| F.1.79. | The IIS shall have the ability for role-based access control (RBAC) for data access using configurations based on user roles with defined permissions for each user role. | Select Your Response | F | 1 | 79 |
| F.1.80. | The IIS shall be capable of adhering to all American Immunization Registry Association (AIRA) business rules to ensure standardization and interoperability. | Select Your Response | F | 1 | 80 |
| F.1.81. | The IIS shall meet all assessments/validations per AIRA AART testing, or be actively progressing towards meeting those test assessments/validations. | Select Your Response | F | 1 | 81 |
| F.1.82. | The IIS shall be capable of meeting all Centers for Disease Control and Prevention (CDC) IIS Functional Standards or be actively progressing towards full compliance, with the ability to provide documentation supporting progress if requested. Additionally, the system must be adaptable to make necessary adjustments if these functionalities change during the contract term. | Select Your Response | F | 1 | 82 |
| F.1.83. | The IIS shall have the ability to configure race and ethnicity codes per jurisdictional policy. | Select Your Response | F | 1 | 83 |
| F.1.84. | The IIS shall have the ability to configure sex and gender identity codes per jurisdictional policy. | Select Your Response | F | 1 | 84 |
| Level 1: User Roles and Permissions | F | 1 | |||
| F.1.85. | The IIS shall have the ability for jurisdictional admin to manage user roles and permissions by task per jurisdictional policy. | Select Your Response | F | 1 | 85 |
| F.1.86. | The IIS shall have the ability for jurisdictional admin to add user roles with distinct permissions. | Select Your Response | F | 1 | 86 |
| F.1.87. | The IIS shall have the ability for jurisdictional admin to modify user roles with distinct permissions. | Select Your Response | F | 1 | 87 |
| F.1.88. | The IIS shall have the ability for jurisdictional admin to inactivate user roles. | Select Your Response | F | 1 | 88 |
| F.1.89. | The IIS shall have the ability for jurisdictional admin to modify permissions to IIS processes and data for specific user roles. | Select Your Response | F | 1 | 89 |
| F.1.90. | The IIS shall have the ability for jurisdictional admin to restrict system functionality by user role. | Select Your Response | F | 1 | 90 |
| F.1.91. | The IIS shall have the ability for jurisdictional admin to restrict authorized user access to data based on user role. | Select Your Response | F | 1 | 91 |
| F.1.92. | The IIS shall have the ability for jurisdictional admin to enable access to standard reports based on user role. | Select Your Response | F | 1 | 92 |
| F.1.93. | The IIS shall have the ability for automatically update all users assigned to a role based on changes made to the "master" role attributes. | Select Your Response | F | 1 | 93 |
| F.1.94. | The IIS shall have the ability for role based user views which align with established role based access control (RBAC) . | Select Your Response | F | 1 | 94 |
| F.1.95. | The IIS shall have the ability to provide a variety of user roles to support the Solution, with each role assigned a unique set of responsibilities and permissions within the system. Example of user roles might include but are not limited to: |
A. Data Quality Manager B. Data Entry Operator C. Data Analyst D. System Administrator E. Audit and Compliance Officer F. Quality Assurance Staff G. Administrator H. Provider I. Health Department Staff J. Read-Only Access K. Audit Staff L. Support Staff
| M. Site Administrator | Select Your Response | F | 1 | 95 | ||||
| Level 1: System Alerts | ||||||||
| F.1.96. | The IIS shall have the ability for jurisdictional admin to manage system alerts. | Select Your Response | F | 1 | 96 | |||
| F.1.97. | The IIS shall have the ability to view global messages upon logging into the application. | Select Your Response | F | 1 | 97 | |||
| F.1.98. | The IIS shall have the ability to electronically notify the applicant of incomplete IIS enrollment information specifying the missing required fields. | Select Your Response | F | 1 | 98 | |||
| F.1.99. | The IIS shall have the ability for jurisdictional admin to edit global messages. | Select Your Response | F | 1 | 99 | |||
| F.1.100. | The IIS shall have the ability for jurisdictional admin to inactivate global messages. | Select Your Response | F | 1 | 100 | |||
| Level 0: Manage Organizations & Facilities | ||||||||
| Level 1: Organization/Facility Search | ||||||||
| F.1.101. | The IIS shall have the ability to search organization/facility information stored in the IIS. | Select Your Response | F | 1 | 101 | |||
| F.1.102. | The IIS shall have the ability for jurisdictional admin to search organizations/facilities by user-defined parameters. | Select Your Response | F | 1 | 102 | |||
| F.1.103. | The IIS shall have the ability to clear and re-enter search criteria when searching for an organization/facility. | Select Your Response | F | 1 | 103 | |||
| Level 1: Add, Edit, Inactivate Organization | ||||||||
| F.1.104. | The IIS shall have the ability for applicant from unauthorized (non-participating/enrolled) organization to enroll electronically for participation in the IIS. | Select Your Response | F | 1 | 104 | |||
| F.1.105. | The IIS shall have the ability for applicant from unauthorized organization to add IIS enrollment information online. | Select Your Response | F | 1 | 105 | |||
| F.1.106. | The IIS shall have the ability for applicant from unauthorized organization to submit IIS enrollment information online. | Select Your Response | F | 1 | 106 | |||
| F.1.107. | The IIS shall have the ability to prevent submission of incomplete IIS enrollment information when required field(s) are missing. | Select Your Response | F | 1 | 107 | |||
| F.1.108. | The IIS shall have the ability to electronically notify the applicant of incomplete IIS enrollment information specifying the missing required fields. | Select Your Response | F | 1 | 108 | |||
| F.1.109. | The IIS shall have the ability to electronically notify applicant that IIS enrollment information has been submitted. | Select Your Response | F | 1 | 109 | |||
| F.1.110. | The IIS shall have the ability for applicant from unauthorized organization to edit rejected IIS enrollment information. | Select Your Response | F | 1 | 110 | |||
| F.1.111. | The IIS shall have the ability for applicant from unauthorized organization to resubmit a rejected IIS enrollment. | Select Your Response | F | 1 | 111 | |||
| F.1.112. | The IIS shall have the ability for jurisdictional admin to manage organization/facility IIS enrollment. | Select Your Response | F | 1 | 112 | |||
| F.1.113. | The IIS shall have the ability for jurisdictional admin to manage organization/facility IIS enrollment status. | Select Your Response | F | 1 | 113 | |||
| F.1.114. | The IIS shall have the ability for jurisdictional admin to inactivate an organization. | Select Your Response | F | 1 | 114 | |||
| F.1.115. | The IIS shall have the ability for jurisdictional admin to reactivate an organization. | Select Your Response | F | 1 | 115 | |||
| F.1.116. | The IIS shall have the ability to store IIS enrollment status for an organization/facility. | Select Your Response | F | 1 | 116 | |||
| F.1.117. | The IIS shall have the ability for jurisdictional admin to inactivate a facility. | Select Your Response | F | 1 | 117 | |||
| F.1.118. | The IIS shall have the ability for jurisdictional admin to reactivate a facility. | Select Your Response | F | 1 | 118 | |||
| F.1.119. | The IIS shall have the ability for jurisdictional admin to electronically approve IIS enrollment. | Select Your Response | F | 1 | 119 | |||
| F.1.120. | The IIS shall have the ability to include reason for rejecting IIS enrollment of an organization. | Select Your Response | F | 1 | 120 | |||
| F.1.121. | The IIS shall have the ability to electronically notify the organization that the submitted enrollment was rejected along with the reason. | Select Your Response | F | 1 | 121 | |||
| F.1.122. | The IIS shall have the ability for jurisdictional admin to manage organization and facility records within the IIS. | Select Your Response | F | 1 | 122 | |||
| F.1.123. | The IIS shall have the ability for jurisdictional admin to add an organization. | Select Your Response | F | 1 | 123 | |||
| F.1.124. | The IIS shall have the ability for jurisdictional admin to modify an organization record. | Select Your Response | F | 1 | 124 | |||
| F.1.125. | The IIS shall have the ability for jurisdictional admin to add a facility. | Select Your Response | F | 1 | 125 | |||
| F.1.126. | The IIS shall have the ability for jurisdictional admin to modify a facility record. | Select Your Response | F | 1 | 126 | |||
| F.1.127. | The IIS shall have the ability to automatically generate unique facility IIS ID. | Select Your Response | F | 1 | 127 | |||
| F.1.128. | The IIS shall have the ability for jurisdictional admin to associate a facility to an organization. | Select Your Response | F | 1 | 128 | |||
| F.1.129. | The IIS shall have the ability for jurisdictional admin to edit association between a facility and organization. | Select Your Response | F | 1 | 129 | |||
| F.1.130. | The IIS shall have the ability to store multiple unique facility site IDs associated with a particular facility (to facilitate matching of facilities between the IIS and other data systems). | Select Your Response | F | 1 | 130 | |||
| F.1.131. | The IIS shall have the ability to capture a facility's mailing address. | Select Your Response | F | 1 | 131 | |||
| F.1.132. | The IIS shall have the ability to capture a facility's shipping address. | Select Your Response | F | 1 | 132 | |||
| F.1.133. | The IIS shall have the ability to enter contact information for the facility contact. | Select Your Response | F | 1 | 133 | |||
| F.1.134. | The IIS shall have the ability to enter contact information for an Desirable contact. | Select Your Response | F | 1 | 134 | |||
| F.1.135. | The IIS shall have the ability to indicate if an organization/facility is a site where immunizations are administered. | Select Your Response | F | 1 | 135 | |||
| F.1.136. | The IIS shall have the ability to save documents (i.e., enrollment/onboarding documents, storage and handling, borrowing, temperature logs, wastage, etc.) to specific organization/facility file folder per policy. | Select Your Response | F | 1 | 136 | |||
| F.1.137. | The IIS shall have the ability for jurisdictional admin to retrieve electronic files from provider file folder. | Select Your Response | F | 1 | 137 | |||
| F.1.138. | The IIS shall have the ability for jurisdictional admin to record notes related to a organization/facility. | Select Your Response | F | 1 | 138 | |||
| F.1.139. | The IIS shall have the ability to flag an organization as participating in VFC and/or other user-defined vaccine program(s). | Select Your Response | F | 1 | 139 | |||
| F.1.140. | The IIS shall have the ability for authorized users (e.g., providers) to send jurisdictional admin updates about their organization / facilities, including but not limited to new facility/site locations and updates to contact information. | Select Your Response | F | 1 | 140 | |||
| Level 1: VFC/Vaccine Program Enrollment | ||||||||
| F.1.141. | The IIS shall have the ability for an organization to submit vaccine program enrollment information electronically. | Select Your Response | F | 1 | 141 | |||
| F.1.142. | The IIS shall have the ability to capture electronic signature for vaccine program enrollment. | Select Your Response | F | 1 | 142 | |||
| F.1.143. | The IIS shall have the ability to access the vaccine program agreement in a separate window from the vaccine program enrollment. | Select Your Response | F | 1 | 143 | |||
| F.1.144. | The IIS shall have the ability to provide link to the blank formatted vaccine program enrollment form. | Select Your Response | F | 1 | 144 | |||
| F.1.145. | The IIS shall have the ability for the jurisdictional vaccine program admin to assign a VFC pin number to a newly enrolled VFC site. | Select Your Response | F | 1 | 145 | |||
| F.1.146. | The IIS shall have the ability to select the type of certified monitoring device being used to record temperatures. | Select Your Response | F | 1 | 146 | |||
| F.1.147. | The IIS shall have the ability for the jurisdictional vaccine program admin to document that a facility has a certificate of calibration for the temperature monitoring device. | Select Your Response | F | 1 | 147 | |||
| F.1.148. | The IIS shall have the ability for the jurisdictional vaccine program admin to approve a vaccine program enrollment. | Select Your Response | F | 1 | 148 | |||
| F.1.149. | The IIS shall have the ability for the jurisdictional vaccine program admin to enter an expiration date for a vaccine program enrollment. | Select Your Response | F | 1 | 149 | |||
| F.1.150. | The IIS shall have the ability for the jurisdictional vaccine program admin to document that the vaccine program facility has a routine and emergency vaccine management plan. | Select Your Response | F | 1 | 150 | |||
| F.1.151. | The IIS shall have the ability for the jurisdictional vaccine program admin to document that a facility participating in VFC has a VFC Coordinator annual training certificate. | Select Your Response | F | 1 | 151 | |||
| F.1.152. | The IIS shall have the ability for the jurisdictional vaccine program admin to document that a facility participating in VFC has a Backup Coordinator annual training certificate. | Select Your Response | F | 1 | 152 | |||
| F.1.153. | The IIS shall have the ability to require the vaccine program facility to indicate the number of vaccine storage units being monitored. | Select Your Response | F | 1 | 153 | |||
| F.1.154. | The IIS shall have the ability to require the vaccine program facility to indicate the types of vaccine storage units being monitored. | Select Your Response | F | 1 | 154 | |||
| F.1.155. | The IIS shall have the ability to require the vaccine program facility to indicate whether they store frozen or ultra-frozen vaccines (e.g., Varicella, MMRV). | Select Your Response | F | 1 | 155 | |||
| F.1.156. | The IIS shall have the ability to enter contact information for the facility Primary Vaccine Coordinator. | Select Your Response | F | 1 | 156 | |||
| F.1.157. | The IIS shall have the ability to enter contact information for the facility Backup Vaccine Coordinator. | Select Your Response | F | 1 | 157 | |||
| F.1.158. | The IIS shall have the ability to enter contact information for the facility vaccine program Agreement Signatory. | Select Your Response | F | 1 | 158 | |||
| F.1.159. | The IIS shall have the ability to capture the day(s) of the week that a vaccine program facility may receive vaccine shipments. | Select Your Response | F | 1 | 159 | |||
| F.1.160. | The IIS shall have the ability to capture the time(s) that a vaccine program facility may receive vaccine shipments. | Select Your Response | F | 1 | 160 | |||
| F.1.161. | The IIS shall have the ability to automatically turn off vaccine ordering capabilities for a facility that does not have an up-to-date vaccine enrollment. | Select Your Response | F | 1 | 161 | |||
| F.1.162. | The IIS shall have the ability to capture required information for VFC clinician: last name, first name, title, medical license number, NPI number, still active with facility, are they a signatory, specialty (e.g., FP, Peds) during the enrollment process. | Select Your Response | F | 1 | 162 | |||
| F.1.163. | The IIS shall have the ability to attach VFC documentation (in multiple formats) such as: VFC training certification, certificate of calibration, medical license, floor design diagram and other documents. | Select Your Response | F | 1 | 163 | |||
| F.1.164. | The IIS shall have the ability to submit vaccine program re-enrollment data electronically. | Select Your Response | F | 1 | 164 | |||
| F.1.165. | The IIS shall have the ability for the jurisdictional vaccine program admin to modify the date for online renewal electronic notifications for each vaccine program facility. | Select Your Response | F | 1 | 165 | |||
| F.1.166. | The IIS shall have the ability to suspend ordering capabilities for a facility pending approval of vaccine program enrollment. | Select Your Response | F | 1 | 166 | |||
| F.1.167. | The IIS shall have the ability to re-activate ordering capabilities for a facility when a vaccine program enrollment is approved. | Select Your Response | F | 1 | 167 | |||
| Level 1: Organization/Facility Outreach | ||||||||
| F.1.168. | The IIS shall have the ability to send electronic communications to organization/facility contacts. | Select Your Response | F | 1 | 168 | |||
| F.1.169. | The IIS shall have the ability to send a final electronic notification reminder, re: renewal, to all VFC facilities per jurisdiction that have not completed the renewal by their expiration date. | Select Your Response | F | 1 | 169 | |||
| F.1.170. | The IIS shall have the ability to notify more than one user at a participating vaccine program facility of any vaccine program notification. | Select Your Response | F | 1 | 170 | |||
| F.1.171. | The IIS shall have the ability to allow authorized users (e.g., jurisdictional admin) to upload, approve, and reject documents according to business rules. | Select Your Response | F | 1 | 171 | |||
| F.1.172. | The IIS shall have the ability for jurisdictional admin to automatically and manually place specific users/organizations/facilities' vaccine ordering abilities on hold until compliance has been met through the submission and approval of required documentation. | Select Your Response | F | 1 | 172 | |||
| Level 0: Manage Users | ||||||||
| Level 1: User Search | ||||||||
| F.1.173. | The IIS shall have the ability for jurisdictional admin to search for user accounts by user-defined criteria. | Select Your Response | F | 1 | 173 | |||
| F.1.174. | The IIS shall have the ability for jurisdictional admin to view all user accounts. | Select Your Response | F | 1 | 174 | |||
| F.1.175. | The IIS shall have the ability for organization admin to search all user accounts associated with their organization. | Select Your Response | F | 1 | 175 | |||
| F.1.176. | The IIS shall have the ability for organization admin to view all user accounts associated with their organization. | Select Your Response | F | 1 | 176 | |||
| Level 1: Add, Edit, Inactivate User | ||||||||
| F.1.177. | The IIS shall have the ability for admin to manage user accounts. | Select Your Response | F | 1 | 177 | |||
| F.1.178. | The IIS shall have the ability for admin to add new users. | Select Your Response | F | 1 | 178 | |||
| F.1.179. | The IIS shall have the ability for admin to modify user accounts. | Select Your Response | F | 1 | 179 | |||
| F.1.180. | The IIS shall have the ability for admin to inactivate user accounts. | Select Your Response | F | 1 | 180 | |||
| F.1.181. | The IIS shall have the ability for organization admin to inactivate user accounts associated with their organization. | Select Your Response | F | 1 | 181 | |||
| F.1.182. | The IIS shall have the ability to store reason for inactivation of user account. | Select Your Response | F | 1 | 182 | |||
| F.1.183. | The IIS shall have the ability for jurisdictional admin to reactivate an inactivated account. | Select Your Response | F | 1 | 183 | |||
| F.1.184. | The IIS shall have the ability for jurisdictional admin to assign a role to authorized users. | Select Your Response | F | 1 | 184 | |||
| F.1.185. | The IIS shall have the ability for organization admin to assign a role to authorized users within their organization. | Select Your Response | F | 1 | 185 | |||
| Level 1: Authentication & Authorization | ||||||||
| F.1.186. | The IIS shall have the ability to authenticate user. | Select Your Response | F | 1 | 186 | |||
| F.1.187. | The IIS shall have the ability to access the system through an authorized username and password. | Select Your Response | F | 1 | 187 | |||
| F.1.188. | The IIS shall have the ability to switch between multiple facilities within the same organization. | Select Your Response | F | 1 | 188 | |||
| F.1.189. | The IIS shall have the ability to view jurisdictional policy agreements. | Select Your Response | F | 1 | 189 | |||
| F.1.190. | The IIS shall support multi-factor authentication as per jurisdictional policy. | Select Your Response | F | 1 | 190 | |||
| Level 1: Password Management | ||||||||
| F.1.191. | The IIS shall have the ability to generate electronic notification to authorized user of account credentials. | Select Your Response | F | 1 | 191 | |||
| F.1.192. | The IIS shall have the ability to electronically notify authorized users of their username. | Select Your Response | F | 1 | 192 | |||
| F.1.193. | The IIS shall have the ability to electronically notify authorized users of their temporary password in a separate notification. | Select Your Response | F | 1 | 193 | |||
| F.1.194. | The IIS shall have the ability to generate electronic notification at periodic intervals to authorized users of their pending account password expiration. | Select Your Response | F | 1 | 194 | |||
| F.1.195. | The IIS shall have the ability for jurisdictional admin to configure the periodic intervals (e.g., 30 days prior, 14 days prior, 7 days prior, etc.) for generation of notifications to authorized users of their pending account password expiration. | Select Your Response | F | 1 | 195 | |||
| F.1.196. | The IIS shall have the ability to support temporary password which will be required to change during initial log in. | Select Your Response | F | 1 | 196 | |||
| F.1.197. | The IIS shall have the ability to support temporary password which will expire as determined by IDPH policy. | Select Your Response | F | 1 | 197 | |||
| F.1.198. | The IIS shall have the ability for users to change their own passwords per program/jurisdiction security policy. | Select Your Response | F | 1 | 198 | |||
| F.1.199. | The IIS shall have the ability for users to reset their password per program/jurisdiction security policy. | Select Your Response | F | 1 | 199 | |||
| F.1.200. | The IIS shall have the ability to prompt users to change their password at time intervals per program/jurisdiction security policy. | Select Your Response | F | 1 | 200 | |||
| Level 0: Support Interoperability | ||||||||
| Level 1: Onboarding | ||||||||
| F.1.201. | The IIS shall have the ability to onboard organizations/facilities to facilitate electronic data exchange. | Select Your Response | F | 1 | 201 | |||
| F.1.202. | The IIS shall have the ability to track an organization's/facility's progress through the onboarding process. | Select Your Response | F | 1 | 202 | |||
| F.1.203. | The IIS shall have the ability to capture electronic health record (EHR) system specification details. | Select Your Response | F | 1 | 203 | |||
| F.1.204. | The IIS shall have the ability to create a unique username to assign to the organizations/facilities during the test phase. | Select Your Response | F | 1 | 204 | |||
| F.1.205. | The IIS shall have the ability to create a unique password to assign to the organizations/facilities during the test phase. | Select Your Response | F | 1 | 205 | |||
| F.1.206. | The IIS shall have the ability to validate that the transport layer between the test site and IIS is functional. | Select Your Response | F | 1 | 206 | |||
| F.1.207. | The IIS shall have the ability to validate system connectivity prior to the submission of test data. | Select Your Response | F | 1 | 207 | |||
| F.1.208. | The IIS shall have the ability to identify data formatting errors during testing. | Select Your Response | F | 1 | 208 | |||
| F.1.209. | The IIS shall have the ability for IIS authorized staff to review and approve onboarding forms. | Select Your Response | F | 1 | 209 | |||
| F.1.210. | The IIS shall have the ability for IIS staff to review and reject onboarding forms. | Select Your Response | F | 1 | 210 | |||
| F.1.211. | The IIS shall have the ability for applicant to edit a rejected onboarding application. | Select Your Response | F | 1 | 211 | |||
| F.1.212. | The IIS shall have the ability for applicant to save a rejected onboarding application. | Select Your Response | F | 1 | 212 | |||
| F.1.213. | The IIS shall have the ability for applicant to resubmit a rejected onboarding application. | Select Your Response | F | 1 | 213 | |||
| F.1.214. | The IIS shall have the ability to compare onboarding application information to current records to determine most current data. | Select Your Response | F | 1 | 214 | |||
| Level 1: Interfaces | ||||||||
| F.1.215. | The IIS shall have the ability to interface with other systems to facilitate electronic data sharing/exchange per jurisdictional policy. | Select Your Response | F | 1 | 215 | |||
| F.1.216. | The IIS shall have the ability to interface with EHR systems. | Select Your Response | F | 1 | 216 | |||
| F.1.217. | The IIS shall have the ability to interface with the CDC Immunization Gateway. | Select Your Response | F | 1 | 217 | |||
| F.1.218. | The IIS shall have the ability to exchange data with CDC Vaccine Tracking System (VTrckS) based on most current CDC Exist Specifications. | Select Your Response | F | 1 | 218 | |||
| F.1.219. | The IIS shall have the ability to order vaccine via electronic interface with VTrckS. | Select Your Response | F | 1 | 219 | |||
| F.1.220. | The IIS shall have the ability to receive vaccine inventory/shipping information. | Select Your Response | F | 1 | 220 | |||
| F.1.221. | The IIS shall have the ability to batch export vaccine inventory for submission to VTrckS or connect to VTrckS via an API. | Select Your Response | F | 1 | 221 | |||
| F.1.222. | The IIS shall have the ability to batch export vaccine ordering information for submission to VTrckS or connect to VTrckS via an API. | Select Your Response | F | 1 | 222 | |||
| F.1.223. | The IIS shall have the ability to batch export facility information. | Select Your Response | F | 1 | 223 | |||
| F.1.224. | The IIS shall have the ability to export vaccine return and wastage data to VTrckS. | Select Your Response | F | 1 | 224 | |||
| F.1.225. | The IIS shall have the ability to receive data through an interface with jurisdictional vital records system. | Select Your Response | F | 1 | 225 | |||
| F.1.226. | The IIS shall have the ability to update IIS data from Vital Records for birth events. | Select Your Response | F | 1 | 226 | |||
| F.1.227. | The IIS shall have the ability to update IIS data from Vital Records for death events. | Select Your Response | F | 1 | 227 | |||
| F.1.228. | The IIS shall have the ability to update IIS data from Vital Records for adoption events. | Select Your Response | F | 1 | 228 | |||
| F.1.229. | The IIS shall have the ability to update IIS data from Vital Records for name change events. | Select Your Response | F | 1 | 229 | |||
| F.1.230. | The IIS shall have the ability to detect if a newborn record is a potential duplicate in the IIS. | Select Your Response | F | 1 | 230 | |||
| F.1.231. | The IIS shall have the ability to use new Vital Record data for matched records to update patient demographic data. | Select Your Response | F | 1 | 231 | |||
| F.1.232. | The IIS shall have the ability to update the IIS with date of death from Vital Records data. | Select Your Response | F | 1 | 232 | |||
| Level 1: Data Exchange | ||||||||
| F.1.233. | The IIS shall have the ability to support real-time data exchange per the CDC HL7 implementation guide. | Select Your Response | F | 1 | 233 | |||
| F.1.234. | The IIS shall have the ability to process an HL7 message. | Select Your Response | F | 1 | 234 | |||
| F.1.235. | The IIS shall have the ability to respond to an HL7 message. | Select Your Response | F | 1 | 235 | |||
| F.1.236. | The IIS shall have the ability to create an HL7 message. | Select Your Response | F | 1 | 236 | |||
| F.1.237. | The IIS shall have the ability to capture IIS Core Data Elements. | Select Your Response | F | 1 | 237 | |||
| F.1.238. | The IIS shall have the ability to store IIS Core Data Elements. | Select Your Response | F | 1 | 238 | |||
| F.1.239. | The IIS shall have the ability to manually correct a submitted record and resubmit for processing. | Select Your Response | F | 1 | 239 | |||
| F.1.240. | The IIS shall have the ability to support data exchange in non-HL7 format. | Select Your Response | F | 1 | 240 | |||
| F.1.241. | The IIS shall have the ability to import bulk patient demographic information into IIS. | Select Your Response | F | 1 | 241 | |||
| F.1.242. | The IIS shall have the ability to import bulk immunization information into IIS. | Select Your Response | F | 1 | 242 | |||
| F.1.243. | The IIS shall have the ability to monitor and troubleshoot data exchange. | Select Your Response | F | 1 | 243 | |||
| F.1.244. | The IIS shall have the ability to view Unsolicited Vaccine Update (VXU) messages submitted by an organization. | Select Your Response | F | 1 | 244 | |||
| F.1.245. | The IIS shall have the ability to view HL7 messages for an organization within a defined date range per jurisdictional policy. | Select Your Response | F | 1 | 245 | |||
| F.1.246. | The IIS shall have the ability to view HL7 Acknowledgment (ACK) messages generated for an organization. | Select Your Response | F | 1 | 246 | |||
| F.1.247. | The IIS shall have the ability to view incoming HL7 Query by Parameter (QBP) messages submitted by an organization. | Select Your Response | F | 1 | 247 | |||
| F.1.248. | The IIS shall have the ability to view Response to Query by Parameter (RSP) messages generated for an organization. | Select Your Response | F | 1 | 248 | |||
| F.1.249. | The IIS shall have the ability to log acknowledgement messages indicating warnings and errors. | Select Your Response | F | 1 | 249 | |||
| F.1.250. | The IIS shall have the ability to retrieve error messages within a specified date range by organization. | Select Your Response | F | 1 | 250 | |||
| F.1.251. | The IIS shall have the ability to retrieve acknowledgment messages within a specified date range by organization. | Select Your Response | F | 1 | 251 | |||
| F.1.252. | The IIS shall have the ability to filter error messages. | Select Your Response | F | 1 | 252 | |||
| F.1.253. | The IIS shall have the ability to filter acknowledgement messages. | Select Your Response | F | 1 | 253 | |||
| F.1.254. | The IIS shall have the ability to sort error messages. | Select Your Response | F | 1 | 254 | |||
| F.1.255. | The IIS shall have the ability to sort acknowledgement messages. | Select Your Response | F | 1 | 255 | |||
| Level 0: Ensure Data Quality | ||||||||
| Level 1: Patient Matching & Deduplication | ||||||||
| F.1.256. | The IIS shall have the ability to prevent duplicate patient records in the IIS database. | Select Your Response | F | 1 | 256 | |||
| F.1.257. | The IIS shall have the ability to support a methodology to automatically identify incoming patient records as potential duplicates. | Select Your Response | F | 1 | 257 | |||
| F.1.258. | The IIS shall have the ability to support a methodology to automatically identify existing patient records as potential duplicates. | Select Your Response | F | 1 | 258 | |||
| F.1.259. | The IIS shall have the ability to automatically consolidate two or more duplicate records. | Select Your Response | F | 1 | 259 | |||
| F.1.260. | The IIS shall have the ability to generate electronic notification of potential duplicates for manual review. | Select Your Response | F | 1 | 260 | |||
| F.1.261. | The IIS shall have the ability to automatically match an incoming patient record with existing records to avoid a duplicate record being created. | Select Your Response | F | 1 | 261 | |||
| F.1.262. | The IIS shall have the ability to set thresholds for patient matching. | Select Your Response | F | 1 | 262 | |||
| F.1.263. | The IIS shall have the ability to view all possible duplicate patient records for an individual patient simultaneously. | Select Your Response | F | 1 | 263 | |||
| F.1.264. | The IIS shall have the ability for jurisdictional admin to edit thresholds to increase the probability of a match. | Select Your Response | F | 1 | 264 | |||
| F.1.265. | The IIS shall have the ability for jurisdictional admin to edit thresholds to reduce the probability of a match. | Select Your Response | F | 1 | 265 | |||
| F.1.266. | The IIS shall have the ability to flag potential duplicate patient records for manual review that cannot be resolved automatically. | Select Your Response | F | 1 | 266 | |||
| F.1.267. | The IIS shall have the ability to view all possible duplicate patient records simultaneously. | Select Your Response | F | 1 | 267 | |||
| F.1.268. | The IIS shall have the ability for admin to manually merge patient records. | Select Your Response | F | 1 | 268 | |||
| F.1.269. | The IIS shall have the ability for organizational/facility user to request to merge patient records from their own organization/facility. | Select Your Response | F | 1 | 269 | |||
| F.1.270. | The IIS shall have the ability to manually flag two or more patient records as potential duplicates. | Select Your Response | F | 1 | 270 | |||
| F.1.271. | The IIS shall have the ability to prevent manual review of records previously indicated as "not a duplicate". | Select Your Response | F | 1 | 271 | |||
| F.1.272. | The IIS shall have the ability to flag a patient as "not a duplicate” during manual review. | Select Your Response | F | 1 | 272 | |||
| F.1.273. | The IIS shall have the ability to maintain "not a duplicate" flag for resolved patient records. | Select Your Response | F | 1 | 273 | |||
| F.1.274. | The IIS shall have the ability to select data elements from the patient records to maintain within the consolidated record. | Select Your Response | F | 1 | 274 | |||
| F.1.275. | The IIS shall have the ability to retain “pre-merged” records for reference. | Select Your Response | F | 1 | 275 | |||
| F.1.276. | The IIS shall have the ability to separate patient records that were incorrectly merged. | Select Your Response | F | 1 | 276 | |||
| F.1.277. | The IIS shall have the ability to analyze and profile data to identify anomalies, outliers, and data quality issues to support data cleansing. It shall provide comprehensive insights into the data, including data completeness, accuracy, consistency, and conformity to predefined rules and standards. | Select Your Response | F | 1 | 277 | |||
| Level 1: Vaccination Event Matching & Deduplication | ||||||||
| F.1.278. | The IIS shall have the ability to prevent potential duplicate vaccination events at the immunization level. | Select Your Response | F | 1 | 278 | |||
| F.1.279. | The IIS shall have the ability to support a methodology to automatically identify incoming vaccination event as potential duplicates. | Select Your Response | F | 1 | 279 | |||
| F.1.280. | The IIS shall have the ability to automatically select the most accurate vaccination event based on deduplication rules. | Select Your Response | F | 1 | 280 | |||
| F.1.281. | The IIS shall have the ability to support a methodology to automatically identify existing vaccination events as potential duplicates. | Select Your Response | F | 1 | 281 | |||
| F.1.282. | The IIS shall have the ability to manually flag duplicate vaccination events for manual review. | Select Your Response | F | 1 | 282 | |||
| F.1.283. | The IIS shall have the ability to display possible duplicate vaccine records for an individual patient. | Select Your Response | F | 1 | 283 | |||
| F.1.284. | The IIS shall have the ability to manually merge a duplicate vaccination event. | Select Your Response | F | 1 | 284 | |||
| F.1.285. | The IIS shall have the ability to manually delete a duplicate vaccination event. | Select Your Response | F | 1 | 285 | |||
| F.1.286. | The IIS shall have the ability to automatically consolidate two or more duplicate vaccination events. | Select Your Response | F | 1 | 286 | |||
| Level 0: Evaluate & Forecast | ||||||||
| Level 1: Clinical Decision Support |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .