Medical Cannabis Patient Registry, Establishment Licensing, etc.

1.2.2 Goals and Objectives: · Ensure full compliance with SDCL 34-20G and ARSD 44:90 through collaborative system development with the State of South Dakota. · Ensure the system is modular, configurable, and scalable to support workflow updates or policy changes. · Provide the ability to securely interface/communicate with various state agency systems for sharing HIPAA related data utilizing FHIR-based APIs· Provide the ability to securely interface with the state’s Seed to Sale tracking software· Ensure data integrity and quality, including support for real-time validation, deduplication, cross-system matching, and correction workflows· Provide access securely via Windows desktop, laptop, or tablet each running the current version of their appropriate operating systems· Provide the ability to produce and consume CSV and XML files, provide and utilize secure web services, and provide role-based control over user permissions. · Provide role-based access controls allowing users to edit and modify information entered into the system by the State or end users· Provide the ability to view and report real time data at statewide and local program level and deliver robust reporting, analytics, and dashboard tools· Provide features allowing patients and establishments to track their progress toward meeting application requirements, including a status bar and the ability to scan their final applications for missing documents· Provide the ability to track all aspects of facility inspections from scheduling to final reporting · Eliminate the need for manual spreadsheet tracking of establishment registrations and all inspection processes · Provide training, technical support, and sustainable maintenance to ensure long-term system effectiveness and user adoption. · The patient registry system must provide the capability to create digital medical cannabis patient and caregiver cards that include validation features for medical cannabis dispensaries and law enforcement officers 1.2.3 Description of Components or Phases: The selected vendor must employ a project management approach that will satisfy the scope of work and incorporate all activities described in the RFP. The selected vendor shall adjust the project management approach or project schedules, as necessary, to collaborate with the Department to successfully execute the project. 1.2.4 Scope of Components or Phases: The selected vendor shall develop and maintain a Project Management Plan (PMP no later than 30 working days following the contract start date). The purpose of the Project Management Plan is to provide a comprehensive baseline of what needs to be achieved by the project, how it is to be achieved, who will be involved, how it will be reported and measured and how information will be communicated with the project. It will serve as a reference for decision and clarifications. All relevant project plans including but not limited to the Communication Plan, Change Management Plan, Staffing Management Plan, Quality Management Plan, Risk Management Plan, Issue Management Plan, Technical Review, Conversion Plan and the Work Breakdown Structure are incorporated into the Project Management Plan. It is a living document that evolves as the project progresses and is updated with the latest relevant information as required. The Project Management Plan may be broken into separate documents, but all documents will be considered sections of the Project Management Plan.All written questions should be sent to: whitney.brunner@state.sd.us. Only emailed questions will be accepted. Each offeror may submit 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#26-0904006-008”. 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