DOH SDIIS RFP 2026_FINAL.docx
DOCX document 255 KB Posted
- Solicitation number
- 26RFP-27-0904002-003
- Issued by
- South Dakota
About this file
This Request for Proposal (RFP) is issued by the South Dakota Department of Health in cooperation with the U.S. Centers for Disease Control and Prevention to solicit proposals for software and professional services to implement and support a new Immunization Information System (SDIIS). The State seeks an internet-based system enabling authorized users real-time access to input, analyze, and report immunization data with configurability for registry functionality. Offerors may propose any combination of three hosting options: vendor-hosted, state-hosted on-premises, or state-hosted on Microsoft Azure as a Platform as a Service solution. The system must replace the existing SDIIS while accepting all legacy data with no loss, maintain current HL7 connections, and establish new interfaces with multiple external systems including the South Dakota Birth Registry, Health Link, VTrckS, Electronic Disease Surveillance System, and Medicaid. The proposal deadline is November 25, 2026, by 11:59 p.m. CST, with an anticipated award decision of January 8, 2027, contract execution by January 29, 2027, and a project start date of February 1, 2027. The initial contract term commences February 1, 2027, and expires May 31, 2032, for a total of approximately five years and four months. Key project milestones include project initiation by March 1, 2027; requirements validation by April 12, 2027; environment setup by June 1, 2027; data conversion completion by August 30, 2027; interface development by October 29, 2027; system testing completion by November 29, 2027; training and user acceptance testing by January 18, 2028; and go-live by March 2, 2028.
The RFP requires detailed proposals addressing project management, scheduling, risk management, data conversion, requirements traceability, communication, testing, training, go-live/cutover, and post-implementation support plans. Proposals must comply with multiple federal and state requirements including HIPAA, CDC standards, web accessibility guidelines, single sign-on integration with South Dakota's identity management system, and comprehensive artificial intelligence disclosure and controls. The offeror must submit a complete Table 1 identifying capability specifications or face disqualification; failure to meet Section 3 requirements must be identified with proposed workarounds or future compliance dates. Offerors must obtain and maintain commercial general liability insurance of at least $1 million per occurrence, professional liability insurance of at least $1 million, business automobile liability insurance of at least $1 million per accident, and workers' compensation insurance as required by law. The contract includes standard State indemnification, termination for convenience with 30 days' notice, termination for breach without notice, termination for appropriation failure with 5 business days' notice, and provisions prohibiting assignment without prior written consent. The State retains ownership of all data and deliverables, and contractors must comply with South Dakota Codified Law restrictions regarding debarment, prohibited entities from specified foreign nations, and non-discrimination requirements. Specific pricing information is not disclosed in the RFP document itself; cost proposals are to be submitted separately by the deadline.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP DOH SDIIS IT Exhibit 10.14.26.docx | DOCX document | |
| BIT Attachment 1 ITSP v6.0.pdf | ||
| Security and Vendor Questions v3.3 Production.docx | DOCX document | |
| Contractor Security Acknowledgement Form 2026_.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
STATE OF SOUTH DAKOTA
INFORMATION TECHNOLOGY (IT) RFP
DEPARTMENT OF HEALTH
600 EAST CAPITOL AVENUE
PIERRE, SOUTH DAKOTA, 57501
South Dakota Immunization Information System (SDIIS)
PROPOSALS ARE DUE NO LATER THAN NOVEMBER 25, 2026 BY 11:59PM CST
RFP #: 27-0904002-003 STATE POC: Nayeema Ahmed EMAIL: sddoh.immunization@state.sd.us
READ CAREFULLY
FIRM NAME: AUTHORIZED SIGNATURE:
ADDRESS: TYPE OR PRINT NAME:
CITY/STATE: TELEPHONE NO:
ZIP (9 DIGITS): FAX NO:
E-MAIL:
PRIMARY CONTACT INFORMATION
CONTACT NAME:
TELEPHONE NO:
| FAX NO: |
| E-MAIL: |
Version 1.1 August 29, 2016 1
| UPDATED APRIL 13, 2026 V5.4 |
| 13 |
1 General Information
1.1 Purpose of Request for Proposal (RFP)
1.1.1 Background:
The South Dakota Department of Health (DOH), in cooperation with the U.S. Centers for Disease Control and Prevention (CDC), is soliciting proposals from qualified sources of supply for software and professional services to implement and support an Immunization Information System (IIS).
Goals and Objectives:
The system will be internet based allowing authorized users real-time access to input, analyze, and report immunization data. The system will be configurable at SDIIS level, allowing authorized stakeholders to easily update fields and tables for required changes, updates, and reporting associated with registry functionality.
The State is open to more than one hosting model. An Offeror may propose any of the following Hosting Options, or a combination of them:
(a) Vendor-Hosted—the solution is hosted and operated by the Offeror or its agent in the Offeror’s environment;
(b) State-Hosted (On-Premises)—the solution is hosted by the state on the State’s internal infrastructure;
(c) State-Hosted (Azure PaaS)—the solution is hosted in the State’s Azure cloud tenant as a Platform as a Service (PaaS) solution.
The State has not established a preference among the Hostin Option and will evaluation each proposed Hosting Option on its own merits. Options (b) and (c) are referred to collectively in this RFP as the State-Hosted Options. Requirements applicable to each Hosting Option are set out in Section 4.
The following items provide additional information on particular needs or inherent project issues that will confront the Department and Offerors, and which must be addressed in the Offeror’s proposal, work plan, task deadlines, etc. They are presented here for emphasis and should not be considered an exhaustive list. Overall, the possible expectations of this system include the ability to:
· Meet current performance standards and be user-friendly, configurable, stable and secure
· Accept all data existing in SDIIS with no data loss
· Enter/view immunization data via web
· Interface with SDIIS's Current HL7 connections
· Automate client and service de-duplication
· Manage vaccine inventory and automatically decrement doses when administered
· Manage the new system with existing staff
· Generate ad-hoc reports and extracts
· Run provider-based and geographic-based recall
· Integrate newborn screening data
· Enhance School Nurse functionality
· Enable VFC Functionality (Provider enrollment/management)
· Connect to VTrckS to enable functionality
· Connect to the South Dakota Birth Registry
· Connect to South Dakota Electronic Disease Surveillance System (Maven)
· Enable mobile connection
· Provide Public Portal access
· Enhance public health emergency response and mass vaccination efforts
· Generate reports based on CDC requirements and recommendations
· Provide Clinical Decision Support (CDSi)
· Provide 2D Bar Code Scanner
Connect with the State Health Information Exchange (South Dakota Health Link) via CDC predefined standard for queries relating to immunization queries. These are all SOAP wrapped XML packages, using a two directional SSL certificate. Health Link can also accept the following message types and versions:
· HL7 2.5.1
· RSP^K11
· QBP^Q11
1.1.3 Description of Components or Phases:
This project will replace the State's existing Immunization Information System. The scope includes configuration of the proposed solution, conversion of all legacy SDIIS data with no data loss, continuity of existing HL7 connections and establishment of new interfaces, training of State and external users, and transition to ongoing operations and support. The project will be delivered in the following phases: initiation and planning; requirements validation and configuration design; environment setup; data conversion; interface development and testing; system and user acceptance testing; training; go-live and cutover; and post-implementation stabilization. The Offeror must describe how its proposed approach addresses each phase and must reflect these phases in the project plan and schedule required by Section 6.5.
1.1.4 Scope of Components or Phases:
The following outlines year one activities to provide a scope of general project activities. These dates assume an anticipated award decision of January 8, 2027, contract execution on or before January 29, 2027, and a project start date of February 1, 2027, consistent with Section 1.3 Schedule of Activities and Section 2 Length of Contract. All dates are indicative of the State’s expected sequence and are contingent on the actual date of contract execution; the offeror must propose its own schedule in the project plan required by Section 6.5.
· Complete project initiation, including the project plan, project schedule, risk management plan, communication plan, and confirmation of State and Offeror project roles, by March 1, 2027.
· Validate functional and technical requirements, confirm the technical architecture for the awarded Hosting Option, and complete configuration design sessions with Immunization Program staff by April 12, 2027.
· Stand up development, test, training, and production environments, complete single sign-on integration, and complete initial security review by June 1, 2027.
· Complete extraction, mapping, and trial conversion of all legacy SDIIS data, including resolution of duplicate patient and vaccination records, with reconciliation reports demonstrating no data loss, by August 30, 2027.
· Maintain all existing HL7 connections and complete development and testing of interfaces to the South Dakota Birth Registry, South Dakota Health Link, VTrckS, the South Dakota Electronic Disease Surveillance System, newborn screening, and Medicaid by October 29, 2027.
· Complete system integration, functional, performance, and load testing, and pass the required web application vulnerability scan, by November 29, 2027.
· Deliver training for State staff, provider users, and school nurse users, and complete user acceptance testing with feedback incorporated, by January 18, 2028.
· Complete final data conversion, go-live and cutover to the new system, and begin post-implementation stabilization support by March 2, 2028.
If contract execution occurs later than January 29, 2027, the milestone dates above will shift by the corresponding number of days, and the Offeror’s project schedule will be adjusted accordingly through the change process described in the contract.
1.2 Issuing Office and RFP Reference Number
The South Dakota Department of Health (“Agency”) is the issuing office for this document and all subsequent addenda relating to it, on behalf of the State of South Dakota (“State”). The reference number for this transaction is RFP# 27-0904002-003. This reference number must be referred to on all proposals, correspondence, and documentation relating to this RFP. For purposes of this RFP, the State’s centralized IT agency, the Bureau of Information and Technology (“BIT”), must approve all IT related purchases.
1.3 Schedule of Activities (Subject to Change)
All deadlines in the Schedule of Activities are due by 11:59 p.m. CST. The Schedule of Activities for this RFP is as follows:
| RFP Publication | October 21, 2026 |
| Deadline for Letter of Intent to Respond | November 4, 2026, by 11:59pm CST |
| Deadline for Submission of Written Inquiries | November 4, 2026 by 11:59pm CST |
| Deadline for Responses to offeror Questions | November 13, 2026 |
(Limit 50 questions per offeror)
| Deadline for Proposal Submission | November 25, 2026 by 11:59pm CST |
| Discussions / Technical Review | December 9-18, 2026 |
| Demonstrations and presentations | December 18, 2026 |
| Anticipated Award Decision/Contract Negotiation | January 8, 2027 |
1.4 Letter of Intent
All interested offerors must submit a Letter of Intent to respond to this RFP.
The Letter of Intent must be submitted to the Agency via email at sddoh.immunization@state.sd.us by the date and time indicated in Section 1.3 Schedule of Activities. Please place the following in the subject line of your email: “Letter of Intent for RFP# 27-0904002-003”.
1.5 Submitting a Proposal
All proposals must be completed and received by the Agency by the date and time indicated in Section 1.3 Schedule of Activities.
Proposals received after the Deadline for Proposal Submission will be late and ineligible for consideration.
All proposals must be signed, in ink or electronically, by a representative of the offeror who is legally authorized to bind the offeror to the proposal. Proposals that are not properly signed may be rejected. The offeror’s proposal must be prepared pursuant to the requirements of Section 6 Proposal Submission Requirements of this RFP.
The State will only accept electronic proposals via email.
Each offeror must provide an electronic version of the proposal. The electronic version should be provided in MS Word or in PDF format to Nayeema Ahmed (sddoh.immunization@state.sd.us). The email, including attachments, must be limited to 20MB in size.
No proposal will be accepted from, or no contract or purchase order will be awarded to, any person, firm, or corporation that is in arrears upon any obligations to the State of South Dakota, or that otherwise may be deemed irresponsible or unreliable by the State of South Dakota.
1.6 Certification Regarding Debarment, Suspension, Ineligibility, and Voluntary Exclusion – Lower Tier Covered Transactions
By signing and submitting this proposal, the offeror certifies that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation, by any Federal department or agency, from transactions involving the use of Federal funds. Where the offeror is unable to certify to any of the statements in this certification, the offeror shall attach an explanation to its offer.
1.7 Non-Discrimination Statement
The State of South Dakota requires that all contractors, vendors, and suppliers doing business with any State agency, department, or institution, provide a statement of non-discrimination. By signing and submitting their proposal, the offeror certifies they do not discriminate in their employment practices with regard to race, color, creed, religion, age, sex, ancestry, national origin, or disability.
1.8 Restriction of Boycott of Israel
For contractors, vendors, suppliers, or subcontractors with five (5) or more employees who enter into a contract with the State of South Dakota that involves the expenditure of one hundred thousand dollars ($100,000) or more, by submitting a response to this solicitation or agreeing to contract with the State, the bidder or offeror certifies and agrees that the following information is correct:
The bidder or offeror, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, has not refused to transact business activities, has not terminated business activities, and has not taken other similar actions intended to limit its commercial relations, related to the subject matter of the bid or offer, with a person or entity on the basis of Israeli national origin, or residence or incorporation in Israel or its territories, with the specific intent to accomplish a boycott or divestment of Israel in a discriminatory manner. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or offeror on this project and terminate any contract awarded based on the bid or response. The successful bidder or offeror further agrees to provide immediate written notice to the contracting executive branch agency if during the term of the contract it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination.
1.9 Certification Relating to Prohibited Entity
For contractors, vendors, suppliers, or subcontractors who enter into a contract with the State of South Dakota by submitting a response to this solicitation or agreeing to contract with the State, the bidder or offeror certifies and agrees that the following information is correct:
The bidder or offeror, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, is not a prohibited entity, regardless of its principal place of business, that is ultimately owned or controlled, directly or indirectly, by a foreign national, a foreign parent entity, or foreign government from China, Iran, North Korea, Russia, Cuba, or Venezuela, as defined by South Dakota Codified Law § 5-18A. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or offeror on this project and terminate any contract awarded based on the bid or response. The successful bidder or offeror further agrees to provide immediate written notice to the contracting executive branch agency if during the term of the contract it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination and would be cause to suspend and debar a business under SDCL § 5-18D-12.
1.10 Modification or Withdrawal of Proposals
Proposals may be modified or withdrawn by the offeror prior to the established due date and time.
No oral, telephonic, telegraphic or facsimile responses or modifications to informal, formal bids, or Request for Proposals will be considered.
1.11 Questions Regarding RFP
All written questions should be sent to: sddoh.immunization@state.sd.us, only emailed questions will be accepted.
Each offeror may submit up to fifty (50) questions via email concerning this RFP to obtain clarification of requirements. No questions will be accepted after the date and time indicated in the above schedule of activities. Email questions to the email address listed above with the subject line “RFP#27-0904002-003”. The questions and their answers will be sent to all offerors that submitted Letters of Intent, submitted questions, or requested the questions and answers via email before the proposal submittal date and will be sent by the date and time indicated in the above calendar of events. Offeror may not rely on any other statements, either of a written or oral nature, that alter any specification or other term or condition of this RFP that have not originated from the SD RFP Project Contact. Offerors will be notified in the same manner as indicated above regarding any modifications to this RFP. Offerors and their agents may not contact any state employee other than the buyer of record regarding any of these matters during the solicitation and evaluation process. Inappropriate contacts are grounds for suspension and exclusion from specific procurements.
1.12 Prohibition on Solely AI-Generated Submissions
All questions, responses, and proposals submitted in response to this RFP must be thoroughly vetted, verified, and validated by the vendor's human staff. Submissions that are solely generated by Artificial Intelligence (AI) without substantive human review and oversight are strictly prohibited and may result in the disqualification of the proposal or rejection of the submitted questions.
1.13 Proprietary Information
The proposal of the successful offeror(s) becomes public information. Proprietary information can be protected under limited circumstances such as client lists and non-public financial statements. An entire proposal may not be marked as proprietary. Offerors must clearly identify in the Executive Summary and mark in the body of the proposal any specific proprietary information they are requesting to be protected. The Executive Summary must contain specific justification explaining why the information is to be protected. Proposals may be reviewed and evaluated by any person at the discretion of the State. All materials submitted become the property of the State of South Dakota and may be returned only at the State's option.
1.14 Length of Contract
The initial term of the contract will commence on February 1, 2027, and expire on May 31, 2032, for a total term of approximately five (5) years and four (4) months.
1.15 Site Visit
If site visits are required, they will be scheduled before the submission of the proposal. Site visits will be made at the offeror’s expense.
1.16 Presentations/Demonstrations
At the State’s discretion, the State may require a presentation or demonstration by an offeror to clarify a proposal. However, the State may award a contract based on the initial proposals received without a presentation or demonstration by the offeror. If presentations or demonstrations are required, they will be scheduled after the submission of proposals. Presentations and demonstrations will be made at the offeror’s expense.
1.17 Discussions
At the State’s discretion, the offeror may or may not be invited to have discussions with the State. The discussions can be before or after the RFP has been submitted. Discussions will be made at the offeror’s expense.
1.18 Technical Review
At the State’s discretion, the State may require a technical review of the offeror based on the offeror’s proposal and response to the Security and Vendor Questionnaire.
1.19 Negotiations
This process is a Request for Proposal/Competitive Negotiation process. Each proposal will be evaluated, and each respondent will be available for negotiation meetings at the State’s request. The State reserves the right to negotiate on any component of every proposal submitted. From the time the proposals are submitted until the formal award of a contract, each proposal is considered a working document and as such, will be kept confidential. The negotiation discussions will also be held as confidential until such time as the award is completed.
2 Standard Contract Terms and Conditions
Any contract or agreement resulting from this RFP will include the State’s standard terms and conditions as listed below, the State’s standard Information Technology (“IT”) contract terms listed in Appendix A, and any additional terms and conditions as negotiated by the parties. The offeror must indicate in its response any issues it has with specific contract terms. If the offeror does not indicate that there is an issue with a specific contract term, then the offeror will be deemed to have accepted the contract terms as written.
2.1 The Contractor will perform those services described in the Scope of Work, attached hereto as Section 3 of the RFP and by this reference incorporated herein.
2.2 The Contractor’s services under this Agreement will start on , and end on , unless terminated sooner pursuant to the terms of the Agreement.
2.3 The Contractor will not use State equipment, supplies, or facilities. The Contractor will provide the State with its Employer Identification Number, Federal Tax Identification Number, or Social Security Number upon execution of this Agreement.
2.4 The State will make payment for services upon satisfactory completion of the services. The TOTAL CONTRACT AMOUNT is an amount not to exceed $ . The State will not pay Contractor's expenses as a separate item. Payment will be made pursuant to itemized invoices submitted with a signed state voucher. Payment will be made consistent with SDCL chapter 5-26.
2.5 The Contractor agrees to indemnify the State of South Dakota, its officers, agents, and employees, from and against all claims or proceedings for actions, suits, damages, liabilities, other losses or equitable relief that may arise at least in part as a result of an act or omission in performing services under this Agreement. The Contractor will defend the State of South Dakota, its officers, agents, and employees against any claim, including any claim, action, suit, or other proceeding related to the claim. The Contractor’s obligation to indemnify includes the payment of attorney fees and other costs of defense. In defending the State of South Dakota, its officers, agents, and employees, the Contractor will engage other professionals, subject to the written approval of the State which will not be unreasonably withheld. Notwithstanding the foregoing, the State may, in its sole discretion and at the expense of the Contractor, engage attorneys and other professionals to defend the State of South Dakota, its officers, agents, and employees, or to assist the Contractor in the defense. This section does not require the Contractor to be responsible for or defend against claims or proceedings for damages, liabilities, losses, or equitable relief arising solely from errors or omissions of the State, its officers, agents, or employees.
2.6 During the term of this Agreement, the Contractor will obtain and maintain in force insurance coverage of the types and with the limits as follows:
2.6.1 Commercial General Liability Insurance:
The Contractor will maintain occurrence based commercial general liability insurance or equivalent form with a limit of not less than $1 million for each occurrence. If such insurance contains a general aggregate limit it will apply separately to this Agreement or be no less than two times the occurrence limit. The insurance policy will name the State of South Dakota, its officers and employees, as additional insureds, but liability coverage is limited to claims not barred by sovereign immunity. The State of South Dakota, its officers and employees do not hereby waive sovereign immunity for discretionary conduct as provided by law.
2.6.2 Professional Liability Insurance or Miscellaneous Professional Liability Insurance:
The Contractor will procure and maintain professional liability insurance or miscellaneous professional liability insurance with a limit not less than $1 million.
2.6.3 Business Automobile Liability Insurance:
The Contractor will maintain business automobile liability insurance or equivalent form with a limit of not less than $1 million for each accident. Such insurance will include coverage for owned, hired, and non-owned vehicles.
2.6.4 Workers’ Compensation Insurance:
The Contractor will procure and maintain workers’ compensation and employers’ liability insurance as required by South Dakota or federal law.
Before beginning work under this Agreement, Contractor will furnish the State with properly executed Certificates of Insurance which will clearly evidence all insurance required in this Agreement. In the event a substantial change in insurance, issuance of a new policy, cancellation, or nonrenewal of the policy, the Contractor agrees to provide immediate notice to the State and provide a new certificate of insurance showing continuous coverage in the amounts required. Contractor will furnish copies of insurance policies if requested by the State.
2.7 While performing services under this Agreement, the Contractor is an independent contractor and not an officer, agent, or employee of the State of South Dakota.
2.8 The Contractor agrees to report to the State any event encountered in the course of performance of this Agreement which results in injury to the person or property of third parties, or which may otherwise subject Contractor or the State to liability. The Contractor will report any such event to the State immediately upon discovery.
The Contractor's obligation under this section will only be to report the occurrence of any event to the State and to make any other report provided for by their duties or applicable law. The Contractor’s obligation to report will not require disclosure of any information subject to privilege or confidentiality under law (e.g., attorney-client communications). Reporting to the State under this section will not excuse or satisfy any obligation of the Contractor to report any event to law enforcement or other entities under the requirements of any applicable law.
2.9 This Agreement may be terminated by either party hereto upon thirty (30) days’ written notice. In the event the Contractor breaches any of the terms or conditions of this Agreement, this Agreement may be terminated by the State at any time with or without notice. If termination for a breach is affected by the State, any payments due to the Contractor at the time of termination may be adjusted to cover any additional costs to the State because of the Contractor's breach. Upon termination the State may take over the work and may award another party an agreement to complete the work under this Agreement. If after the State terminates for a breach by the Contractor it is determined that the Contractor was not at fault, then the Contractor will be paid for eligible services rendered and expenses incurred up to the date of termination.
2.10 This Agreement depends upon the continued availability of appropriated funds and expenditure authority from the Legislature for this purpose. If for any reason the Legislature fails to appropriate funds or grant expenditure authority, or funds become unavailable by operation of law or federal funds reductions, this Agreement will be terminated by the State upon five (5) business days’ written notice. The Contractor agrees that termination for any of these reasons is not a default by the State nor does it give rise to a claim against the State or any officer, agent, or employee of the State, and the Contractor waives any claim against the same.
2.11 This Agreement may not be assigned without the express prior written consent of the State. This Agreement may not be amended except in writing, which writing will be expressly identified as a part of this Agreement and be signed by an authorized representative of each of the parties to this Agreement.
2.12 This Agreement will be governed by and construed in accordance with the laws of the State of South Dakota, without regard to any conflicts of law principles, decisional law, or statutory provision which would require or permit the application of another jurisdiction’s substantive law. Venue for any lawsuit pertaining to or affecting this Agreement will be in Circuit Court, Sixth Judicial Circuit, Hughes County, South Dakota.
2.13 The Contractor will comply with all federal, tribal, state, and local laws, regulations, ordinances, guidelines, permits, requirements, and other standards applicable to providing services pursuant to this Agreement and will be solely responsible for obtaining current information on such requirements. Nothing herein will constitute a waiver by the State to any defense to jurisdiction nor will anything under this Agreement constitute an acknowledgement by the State that any tribe has or exercises any jurisdiction over this Agreement or the parties.
2.14 The Contractor may not use subcontractors to perform the services described in this Agreement without the express prior written consent of the State. The Contractor will include provisions in its subcontracts requiring its subcontractors to comply with the applicable provisions of this Agreement, to indemnify the State, and to provide insurance coverage for the benefit of the State in a manner consistent with this Agreement. The Contractor will cause its subcontractors, agents, and employees to comply with applicable federal, tribal, state, and local laws, regulations, ordinances, guidelines, permits, and other standards and will adopt such review and inspection procedures as are necessary to assure such compliance. The State, at its option, may require the vetting of any subcontractors. The Contractor will assist in the vetting process.
2.15 The State reserves the right to reject any person from performing services under this Agreement who the State believes would be detrimental to the services, presents insufficient skills, presents inappropriate behavior, or is considered by the State to be a security risk.
2.16 The Contractor hereby acknowledges and agrees that all reports, plans, specifications, technical data, miscellaneous drawings, software system programs and documentation, procedures, or files, operating instructions and procedures, source code(s) and documentation, including those necessary to upgrade and maintain the software program, and all information contained therein provided to the State by the Contractor in connection with its performance of services under this Agreement will belong to and is the property of the State and will not be used in any way by the Contractor without the written consent of the State. Papers, reports, forms, software programs, source code(s), and other material which are a part of the work under this Agreement will not be copyrighted without written approval of the State.
2.17 The Contractor certifies that neither Contractor nor its principals are presently debarred, suspended, proposed for debarment or suspension, or declared ineligible from participating in transactions by the federal government or any state or local government department or agency. Contractor further agrees that it will immediately notify the State if during the term of this Agreement Contractor or its principals become subject to debarment, suspension, or ineligibility from participating in transactions by the federal government, or by any state or local government department or agency.
2.18 By signing this Agreement, the Contractor certifies and agrees that is has not refused to transact business activities, have not terminated business activities, and have not taken other similar actions intended to limit its commercial relations, related to the subject matter of this Agreement, with a person or entity that is either the State of Israel, or a company doing business in or with Israel or authorized by, licensed by, or organized under the laws of the State of Israel to do business, or doing business in the State of Israel, with the specific intent to accomplish a boycott or divestment of Israel in a discriminatory manner. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to terminate this Agreement. During the term of this Agreement, if the Contractor no longer complies with this certification, the Contractor agrees to provide immediate written notice to the State and agrees such noncompliance may be grounds for termination of this Agreement.
2.19 Pursuant to South Dakota Codified Law § 5-18A, by entering into this Agreement with the State of South Dakota, the Contractor certifies and warrants that the Contractor is not a prohibited entity, regardless of its principal place of business, that is ultimately owned or controlled, directly or indirectly, by a foreign national, a foreign parent entity, or foreign government from China, Iran, North Korea, Russia, Cuba, or Venezuela, as defined by South Dakota Codified Law § 5-18A.
The Contractor agrees that if this certification is false, the State may terminate this Agreement with no further liability to the State. The Contractor further agrees to provide immediate written notice to the State if during the term of the contract it no longer complies with this certification, and the Contractor agrees such noncompliance may be grounds for contract termination and would be cause to suspend and debar a business under SDCL § 5-18D-12.
2.20 Any notice or other communication required under this Agreement will be in writing and sent to the address set forth above. Notices will be given by and to on behalf of the State, and by and to , on behalf of the Contractor, or such authorized designees as either party may from time to time designate in writing. Notices or communications to or between the parties will be deemed to have been delivered when mailed by first class mail, provided that notice of default or termination will be sent by registered or certified mail, or, if personally delivered, when received by such party.
2.21 In the event that any court of competent jurisdiction will hold any provision of this Agreement unenforceable or invalid, such holding will not invalidate or render unenforceable any other provision of this Agreement.
2.22 All other prior discussions, communications, and representations concerning the subject matter of this Agreement are superseded by the terms of this Agreement, and except as specifically provided in this Agreement, this Agreement constitutes the entire agreement with respect to the subject matter.
2.23 The waiver by either party of a breach or violation of any provisions of this Agreement will not operate as, or be construed to be, a waiver of any subsequent breach of the same or other provision of this Agreement.
2.24 Nothing in this Agreement is intended to constitute a waiver of sovereign immunity by or on behalf of the State of South Dakota, its agencies, officers, or employees.
2.25 Neither party will disclose the contents of the Agreement except as required by applicable law or as necessary to carry out the terms of the Agreement or to enforce that party’s rights under this Agreement. The Contractor acknowledges that the State of South Dakota and its agencies are public entities and thus are bound by South Dakota open meetings and open records laws. It is therefore not a breach of this Agreement for the State to take any action that the State reasonably believes is necessary to comply with the South Dakota open records or open meetings laws, including, without limitation, posting this Agreement on the website pursuant to SDCL § 1-27-46.
3 Scope of Work
The following specifications are material requests to be considered for the award. Offeror must complete Table 1 identifying capabilities of requested specifications. Failure to complete Table 1 will result in disqualification of the proposal.
DOH seeks a scalable, extensible information technology solution for health care services and related information management that supports the service delivery of the Immunization Program. DOH expects that program staff, external providers, and clients will be able to capture, as well as efficiently and securely share, information that will be part of a comprehensive client immunization record. The solution must be exceptionally configurable, i.e. it must simultaneously support the broad array of workflows, data collection and use needs, and reporting needs of the Immunization Program which will utilize the solution’s functionality without compromising system performance and availability. The solution must accommodate future changes in DOH organizational configuration, data needs, reporting requirements, etc.
The State will consider any of the Hosting Options described in Section 1.1. Where an Offeror proposes a Vendor-Hosted solution and hosts through an agent or subcontractor, DOH will hold the Offeror accountable for the performance of that hosting agent. The requirements in this Section 3 apply to the proposed solution regardless of the Hosting Option proposed.
System Requirements:
DOH has identified distinct functional requirements associated with the scope of this new solution. Embedded in these requirements are common expectations for modern health and human services IT solutions including:
· An integrated solution that utilizes best practices for public health agencies and Title X programs.
· The ability to implement automated, user-defined workflow and standard practices workflow that can be easily modified by users.
· Flexible and robust user-driven data extraction, manipulation, viewing, reporting and querying.
· Intuitive screen design and menu-driven access tailored to users.
· Integrated analytics across the entire solution enabled by a common data model.
The Offeror is required to understand and provide the most effective and efficient approach to meeting each requirement for the requested solution.
3.1 General
| 3.1.1 | Functions at least 22 hours a day with an additional two hours daily allotted for a routine system backup and maintenance |
| 3.1.2 | Provides web-based, real-time data exchange of information |
| 3.1.3 | Compatible with State of South Dakota Bureau of Information and Technology (BIT) standards http://bit.sd.gov/standards/web.aspx |
| 3.1.4 | Provides data entry rules that ensure accurate and consistent entry of data (e.g. enforces alpha and numeric fields, allows only valid dates, restricts dropdown selections, etc.) |
| 3.1.5 | Maintains Advisory Committee on Immunization Practice (ACIP)-recommended schedules for children, adolescents, adults |
| 3.1.6 | Supports all current mandatory CDC Core Data Elements for immunization registries https://www.cdc.gov/vaccines/programs/iis/core-data-elements/iis-func-stds.html |
| 3.1.7 | Complies with CDC Public Health Information Network (PHIN) standards https://www.cdc.gov/phin/php/standards/index.html |
| 3.1.8 | Interoperable and compatible with State of South Dakota Bureau of Information and Technology (SD BIT) architecture |
| 3.1.9 | Supports all the CDC/NIP Functional Standards for Immunization Registries https://www.cdc.gov/vaccines/programs/iis/func-stds.html |
| 3.1.10 | Maintains ACIP-recommended vaccinations for travel |
3.2 lmport/Export Data to Other Systems
| 3.2.1 | Supports import and export of data in fixed ASCII text, Excel or CSV format |
| 3.2.2 | Utilizes CDC standard for HL7 data exchange |
| 3.2.3 | Supports user queries |
| 3.2.4 | Imports and exports data using user-defined variables and filters |
| 3.2.5 | Rejects records marked as Opt-Out when being electronically transferred from providers |
| 3.2.6 | Supports the following code sets: |
· HL7 Standard Code Set CVX - Vaccines Administered: https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=tradename
· Current Procedural Terminology (CPT): https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cpt
· International Classification of Diseases, Tenth Revision (ICD-10): http://www.cdc.gov/nchs/icd/icd10.htm
· International Classification of Diseases, Tenth Revision, Clinical Modification (ICD-10-CM): https://www.cdc.gov/nchs/icd/icd-10-cm/index.html and other codes in conjunction with function of application.
| 3.2.7 | Supports import of birth and death certificate data using an Application Programming Interface (API) integration between the IIS and South Dakota’s Vital Records system. Also supports import of data using a one-way batch file. |
| 3.2.8 | Supports import of Medicaid |
| 3.2.9 | Supports import of SDIIS legacy data with no data loss. |
| 3.2.10 | Maintain current HL7 connections and implement new connections as needed. Systems currently connection to SDIIS include: |
| Athena |
| ImmsLink |
| NextGen |
| Cerner |
| IronBridge |
| OCHIN/EPIC |
| CorrectTek |
| IZ Gateway |
| OmniSYS |
| CPSI/Evident |
| Mckesson EnterpriseRx |
| Primary Health |
| eClinicalWorks |
| Medicat |
| Progonics |
| EPIC |
| Meditech |
| ReadySet |
| Greenway Health |
| Mosaiq |
| SMP/PrescribeWellness |
| Health Catalyst |
| NetSmart |
| XIFIN |
| 3.2.11 | Supports/provides interface for users to review and resolve issues with records being imported. |
| 3.2.12 | Supports unattended receipt and incorporation of data into the IIS from external sources |
3.3 Audit Trail
| 3.3.1 | Creates audit trails to track all activity pertaining to the system and records |
| 3.3.2 | Captures and displays the date and time at which the patient's record was last updated |
| 3.3.3 | Captures user ID for individual who last updated the record |
| 3.3.4 | Captures user ID that created the record and date and time record created |
| 3.3.5 | Maintains "created by" or any "creation date/record" information when searching/accessing an existing patient |
| 3.3.6 | Ensures any change to the vaccine history will be visually indicated and selected users will have ability to view changes made (what was changed, by whom, and when) |
3.4 De-duplication and Record Merging
| 3.4.1 | Allows user to choose individual fields/values for record merging and de-duplication process |
| 3.4.2 | Utilizes Soundex, pattern angle de-duplication technology |
| 3.4.3 | Facilitates data mining for duplicate entries |
| 3.4.4 | Flags conflicting information at time of record merging or de-duplication to allow user to determine if records should be merged |
| 3.4.5 | Supports reverse record merging as requested |
3.5 Quality Control
| 3.5.1 | Checks for errors in data entry for related fields (e.g. city, county, and zip code) |
| 3.5.2 | Updates United States Postal Service directory provided by the contractor to support address standardization |
| 3.5.3 | Recognizes multiple zip codes to city, multiple counties to city, multiple counties to zip code, and multiple states to zip code (e.g. Some residents have addresses that are physically situated in South Dakota, yet the postal address belongs to a city in a neighboring state, such as Forbes, ND, or Browns Valley, MN) |
| 3.5.4 | Provides alerts for administration-related errors/events including, but not limited to errors in (i) route of administration, (ii) dosage, (iii) age at administration, (iv) inappropriate intervals, (v) medical contraindications including allergies and adverse reactions to previous doses and exemptions, and (vi) when administration date falls after vaccine expiration date |
| 3.5.5 | Links all related fields to avoid inappropriate/incorrect combinations (e.g., vaccine fields such as type, manufacturer, and brand name) |
| 3.5.6 | Provides warning messages in support of administration decision data (e.g., invalid dose for patient, contraindication, prior immunity) |
| 3.5.7 | Refuses multiple entries of the same inventory lot number with different expiration dates |
| 3.5.8 | Requires administration date to be no later than current date, and no earlier than the patient's birthdate |
| 3.5.9 | Refuses two immunization records of the same type or same series on the same date to be entered |
| 3.5.10 | Supports option to designate Vaccines For Children (VFC) vaccine inventory unavailable for administration to non-VFC eligible patients |
| 3.5.11 | Provides warning message when VFC vaccine is administered to a private patient or private vaccine to a VFC patient |
| 3.5.12 | Provides administrators ability to manually de-duplicate flagged records |
| 3.5.13 | Provides an automated system data monitoring capability to review input data to ensure completeness, accuracy, and validity |
3.6 Disaster Recovery
| 3.6.1 | Facilitates ongoing automatic bi-directional synchronization between the operational and redundant off-site disaster recovery database servers using a secure connection. For State-Hosted Options, the offeror must describe how this capability operates within the State’s infrastructure and identify which components the State would be expected to provide. |
| 3.6.2 | Performs automated back-up procedures for all data |
3.7 Ease of Use
| 3.7.1 | Requires unique ID for each user, provider site and organization |
| 3.7.2 | Calculates age and displays in year/month/day format (e.g., 2 years 4 months 3 days) |
| 3.7.3 | Provides Boolean and wildcard searching |
| 3.7.4 | Ability to conduct and narrow search on multiple related fields |
| 3.7.5 | Provides selection of "other" enabling free text data entry when data are not in a pre-defined list |
| 3.7.6 | Allows user to sort by any column header |
| 3.7.7 | Maintains scrollable text fields or multiple lines with text wrapping to allow viewing of all data as necessary |
| 3.7.8 | Provides pick calendar for date fields |
| 3.7.9 | Links pre-defined/previously entered data and automatically populates related fields (e.g., zip code populates city) |
| 3.7.10 | Function key available to repeat previously entered data within a record (e.g., same immunization administration date for multiple vaccinations) |
3.8 Engineered for Performance
| 3.8.1 | Retains online (real-time) lifetime data access for a minimum of five (5) million patients with capacity to upgrade hardware |
| 3.8.2 | Provides performance capacity to meet peak use (e.g., not less than 1,000 simultaneous users) with at most a three (3) second response time for web page crawls. |
| 3.8.3 | Allows for connection pooling (multiple users share a single database connection) |
| 3.8.4 | Provides reasonable performance for end-users with dial-up connection over a satellite link |
| 3.8.5 | Operates in all supported browsers for Mac and PC (e.g., Edge, Chrome, Safari, and Firefox) |
3.9 User/Site/Organization Relationships
| 3.9.1 | Allows for multiple users to be associated with a single facility |
| 3.9.2 | Allows single users to be associated with multiple facilities |
| 3.9.3 | Allows multiple facilities to be associated with one organization |
| 3.9.4 | Allows one facility to be associated with multiple organizations |
3.10 Help and Tutorial
| 3.10.1 | Provides complete, indexed help guide and tutorial document for users |
| 3.10.2 | Provides fully integrated online help system and tutorial |
| 3.10.3 | Offers content and context sensitive online help |
| 3.10.4 | Maintains index help system to facilitate search capabilities |
| 3.10.5 | Provides user quick guides throughout application to support most common data entry or search issues |
| 3.10.6 | Provides web-based “sandbox” that mirrors actual web application for training and demonstration purposes |
3.11 GIS Capabilities
| 3.11.1 | Provides Geographic Information System (GIS) capability, including the ability to monitor trends in specific populations or geographic areas |
| 3.11.2 | Allows selected users to create GIS reports by selected variables |
| 3.11.3 | Allows for geo-coding for addresses |
| 3.11.4 | Allows integration with and the use of State GIS resources, maps, and layers. |
System Administrator Capabilities:
3.12 Add, Edit, and Configure Data Elements
| 3.12.1 | Allows ability to add or edit data elements |
| 3.12.2 | Maintains ability to identify minimum required fields to create/establish patient records |
| 3.12.3 | Gives State system administrator option to modify vaccine schedules, recommendations, and vaccine types |
3.13 Sets, Deletes, and Modifies User Profiles and Security
| 3.13.1 | Maintains a variety of user profiles that allows delineation of access privileges (e.g. read/write access vs. read-only access) |
| 3.13.2 | Allows addition, deletion, and modification of user profiles and users |
| 3.13.3 | Performs processes to identify, update and deactivate providers and associated information |
| 3.13.4 | Ensures ability to determine use of system by authorized users (providers, schools, other users) |
| 3.13.7 | Sets data elements for record merging, updating, and de-duplication |
Security Requirements:
3.14 User
| 3.14.1 | The system must implement a federated identity architecture that segregates authentication by user persona, either by separate login pages or by dynamically routing public citizens to mySD Single Sign-On (SSO) via OpenID Connect (OIDC) and state employees, providers, and contractors to the state-managed Microsoft Entra ID tenant. All authentication must be delegated to these authoritative Identity Providers (IdPs); the local system is strictly prohibited from storing user passwords. |
| 3.14.2 | Allows only authorized administrative users to create, delete, modify, and update security information on users of the system |
| 3.14.3 | Enforces access to application functions governed via role- and user-based security levels. Security definable down to individual data elements/fields (e.g., “hide," “view," "edit," identify required fields, other) |
| 3.14.4 | Utilizes/provides automated tools to ensure information available to users is compliant with their defined role and access privileges |
| 3.14.5 | Gives only authorized users the ability to edit historical information |
| 3.14.6 | Guarantees log-in audit trail information is accessible and searchable only by System Administrators |
| 3.14.7 | Maintains site-based and administrative roles |
| 3.14.8 | Maintains online assistance for end-user to remember password with security verification |
3.15 Data
| 3.15.1 | Ensures that all data transmissions are encrypted (minimum 256-bit encryption) |
| 3.15.2 | Ensures acceptable system response time |
3.16 System/Application
| 3.16.1 | Follows HIPAA Privacy and Security Rules for Covered Entities http://www.hhs.gov/ocr/privacy/hipaa/understanding/coveredentities/index.html | |
| 3.16.2 | Limits sign-on capability to single workstation at a time | |
| 3.16.3 | Ensures system passwords shall be non-printing and non-displaying | |
| 3.16.4 | Requires changing password at an administrator-set interval, otherwise user locked-out of system, and System Administrator will have to validate and provide access | |
| 3.16.5 | Flags Site System Administrator for, at minimum, semi-annual review | of user roles and access rights |
| 3.16.6 | Identifies and notifies users who violate system policies and standards and terminates the violators’ access to the system |
Patient Record Management Requirements:
3.17 Identify/Search Patient Record
| 3.17.1 | Supports functionality to conduct record search using single field or advanced search using multiple fields |
| 3.17.2 | Supports birthdate search using month (xx), day (xx), year (xx) as separate parameters |
| 3.17.3 | Utilizes sounds values for names (first, last, middle) |
| 3.17.4 | Utilizes pick list with minimum patient information to narrow search if multiple names appear |
| 3.17.5 | Displays patient demographic information as default upon completion of search |
3.18 Create, Delete, Modify, or Update Patient Records
| 3.18.1 | Supports use and capture of other names for all parties (aliases/nicknames for first, middle, last, maiden names) including ability to search, de-duplicate, and generate reports |
| 3.18.2 | Supports multiple addresses and identifies type for all parties (parent, guardian, patient, provider, others; mailing, location, primary, secondary; parent/guardian vs. custodian) and maintains history of all addresses |
| 3.18.3 | Includes all address information: street name and number, PO Box number, apartment number, city, state, zip, geocode, county, country |
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 .