AHCA RFI 025-25-26 Addendum No.2.pdf

AHCA RFI 025-25/26

ADDENDUM NO. 2

AHCA RFI 025-25/26, Addendum No. 2, Page 1 of 1

ITEM 1

Title: Electronic Licensing System Replacement

This addendum to the subject Request for Information (RFI) provides answers to written questions received by the Agency below. All other terms and conditions of the RFI remain in effect.

REMAINDER OF PAGE INTENTIONALLY LEFT BLANK

ADDENDUM 2

QUESTIONS TEMPLATE

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

1 Rotation Software, Inc. Does the Agency anticipate that a future procurement will require full FedRAMP authorization, or would solutions leveraging compliant cloud providers be considered?

FedRAMP is encouraged but not required.

2 Rotation Software, Inc. Is the Agency primarily evaluating established COTS licensing platforms, or is there openness to configurable SaaS solutions tailored to the Agency’s workflows?

The Agency is open to all solutions.

3 Rotation Software, Inc. Does the Agency anticipate opportunities for vendors to participate as implementation partners alongside platform providers?

Possibly.

4 Rotation Software, Inc. Is there an expected timeline for the next step following this RFI, including a potential RFP? No.

5 Deltek In 2022, the Florida Department of Health, Division of Medical Quality Assurance, issued RFI DOH21 012 regarding licensing and regulatory system replacement. Could you please confirm whether the current RFI is separate from that prior initiative, or if it is related to or informed by the earlier DOH RFI?

This is not related to a DOH initiative.

6 Counterpoint Consulting Page 5, Section

III.C.3

Licensing Workflows: Can you provide additional detail on the most complex licensing workflows today, particularly where multiple departments or approval steps are involved, and where you see the greatest opportunity for automation? (Reference: Page 5, Section III.C.3 – Automated Workflows)

These details can be addressed during a future solicitation. For now, please provide the best infromation available that will assist the Agency in determining a procurement approach.

7 Counterpoint Consulting Page 5, Section

III.D.1

Integration Landscape: Can you elaborate on the expected integration landscape, including key upstream and downstream systems such as DataMarts, enterprise data warehouses, and financial systems, and whether near real-time integration is a requirement? (Reference: Page 5, Section III.D.1 – Integration with DataMarts and EDW)

At a minimum, the Agency expects APIs capable of sending and receiving information and the ability for other applications/databases to extract data from the licensing system.

8 Counterpoint Consulting Page 5, Section

III.C.1

Applicant Experience and Self-Service: How does the Agency define success for the applicant's experience in the future system, particularly in areas such as self-service, application status visibility, and the use of tools like chatbots or guided workflows?

(Reference: Page 5, Section III.C.1 – Digital Application Process)

These details can be addressed during a future solicitation. For now, please provide the best infromation available that will assist the Agency in determining a procurement approach.

9 Counterpoint Consulting 4.FedRAMP Authorization Level and Scope Can the Agency clarify the required FedRAMP level (Low, Moderate, or High)?

Additionally, is FedRAMP authorization required at the application (SaaS) level, the underlying cloud platform level, or both?

FedRAMP is encouraged but not required.

10 Counterpoint Consulting Deployment and Operating Model: Does the Agency envision a fully vendor hosted SaaS solution, or would a single tenant or government owned / contractor operated deployment within a FedRAMP authorized environment be acceptable?

The Agency is open to all solutions.

11 Counterpoint Consulting User Volumes: Can the Agency provide estimated counts for internal users, external applicants/licensees?

About 400 internal users will use the product. External users will vary but the Agency has over 50,000 providers.

12 IntegrityPro Consulting, LLC I / II Does the Agency anticipate releasing a formal solicitation following this RFI, and if so, what is the estimated timeline?

At this time, the Agency does not have an anticipated timeframe for releasing a solicitation. All formal competitive soliciations will be posted on the Vendor Information Portal.

13 IntegrityPro Consulting, LLC I Is the Agency considering a single-vendor SaaS platform or a multi-vendor/modular approach for the replacement solution?

The Agency is open to all solutions.

14 IntegrityPro Consulting, LLC II Does the Agency intend to procure this solution through an existing contract vehicle (e.g., state term contracts, NASPO, GSA), or via a new standalone procurement?

The method of procurement is undetermined.

15 IntegrityPro Consulting, LLC II / III To what extent has the current system been customized versus configured, and what lessons learned should inform the replacement approach?

There are many differences between provider types so the system needs to be configurable at that level.

16 IntegrityPro Consulting, LLC II.B Does the Agency expect vendors to perform data cleansing, normalization, and deduplication as part of migration?

Not at this time.

17 IntegrityPro Consulting, LLC II.C How does the Agency envision managing master data (e.g., providers, facilities, licenses) across systems?

Still researching possibilities.

18 IntegrityPro Consulting, LLC III / IV.D Can the Agency provide a list of all systems that currently integrate with VERSA, including DataMarts and EDW dependencies?

No, but it's several dozen at least.

19 IntegrityPro Consulting, LLC IV.C.3 Which processes are highest priority for automation at go-live versus phased implementation?

Work distribution and applications processing ease would be high priorities.

20 IntegrityPro Consulting, LLC IV.C How many distinct user personas are currently supported by the existing system (e.g., applicants, reviewers, inspectors), and what are their primary roles and key pain points?

There are pain points throughout all roles and which roles the Agency will keep depend on the selected solution.

21 IntegrityPro Consulting, LLC VI.F Has the Agency established an estimated budget range for this initiative, including implementation and ongoing SaaS operations?

No.

AHCA RFI 025-25/26, ADDENDUM 2, Page 1 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

22 GL Solutions Internal user counts We have a named-user licensing structure. Based on staff with back-office access regardless of concurrency, how many internal users does AHCA anticipate for the replacement system, broken out if possible by role (for example: licensing/review, inspections, enforcement/case management, finance, supervisors/managers, reporting, IT/system administration, and read-only users)?

The Agency expect around 400 active users.

23 GL Solutions License and transaction volumes Please provide a list of the health facility license, permit, registration, or provider/facility types currently managed in Versa, along with approximate active counts for each. If available, please also provide approximate annual transaction volumes by type for new applications, renewals, amendments/changes, closures/inactivations, and verifications.

The Agency has roughly 50,000 transactions a year and over 30 provider types. More information can be found: https://ahca.myflorida.com/health-quality-assurance/bureau-of-health-facility-regulation

24 GL Solutions Inspection volumes and inspection types Please provide AHCA’s approximate annual inspection volume and the number of distinct inspection types or workflows currently in use or anticipated for the new solution. If available, please break out volumes by type such as initial, routine, complaint-driven, follow-up/reinspection, or other categories used by the Agency.

Roughly 22,000 inspections are done a year and about 10 different inspection types.

25 GL Solutions Mobile inspection scope How many inspectors and supervisors are expected to use the system? Does AHCA anticipate mobile inspection capability as part of the future solution, and if so, is offline capability desired? Approximately how many field devices and unique inspection forms/checklists would be in scope?

Yes the Agency anticipate utilizing mobile inspection capabilities that can be used offline when necessary. 500 devices is a rough estimate of what may be needed.

26 GL Solutions Case management and enforcement scope Please clarify whether complaints, investigations, deficiencies/plans of correction, enforcement actions, and related case management workflows are in scope for the replacement solution. If so, please provide approximate annual volumes and the number of distinct case or enforcement types.

The Agency is open to all solutions regarding licensure and enforcement integration, but the preference is a single solution.

27 GL Solutions Interfaces and directionality The RFI notes that the current Versa system is integrated with other Agency systems.

Please provide a list of current and anticipated interfaces, identifying for each connected system whether the interface is inbound, outbound, or bi-directional, the expected exchange frequency (real-time, scheduled batch, ad hoc, etc.), and whether DataMart and/or Enterprise Data Warehouse feeds are in scope.

At a minimum the Agency expect API's capable of sending and receiving information and the ability for other applications/databases to extract data from the licensing system.

28 GL Solutions Data conversion detail Beyond the 265GB Oracle database identified in the RFI, please provide any available data conversion metrics such as approximate number of tables/objects, years of historical data to be migrated, approximate volume of attachments/images/documents, whether content resides outside the Oracle database, and whether AHCA anticipates full historical migration or a phased/archive approach.

This will vary depending on the chosen system, but ideally the Agency will be able to do as much as possible in the selected system.

29 GL Solutions Financial functionality and volumes Please clarify whether invoicing, hourly rate submissions, payment processing, refunds/adjustments, and related financial workflows are in scope for the replacement system. If so, please provide approximate annual transaction volumes and identify any downstream financial or payment-related systems involved.

This will vary based on the chosen system, but some level of interaction with other financial systems will be required.

30 GL Solutions Reporting, communications, and portal volume Please provide approximate counts for standard reports, dashboards, ad hoc reporting expectations, notices/correspondence templates, and communication channels in scope (email, SMS, letters, portal messages, etc.). If available, please also provide any estimate of external applicant/licensee portal user volume and whether the chatbot is expected to be informational only or integrated with application/status data.

This will vary based on the chosen system, but there is the expectation to generate many different correspondences and reports, whether created internally or externally, will need to be robust.

31 System Automation How many AHCA staff users will access the system? Please provide a breakdown of the number of AHCA employees that will be using the new solution by AHCA program, role, as well as which ones will be performing mobile inspections.

The Agency expect around 400 active users of the licensure system and the system will need to integrate with a federal inspection system that will have roughly 500 users.

32 System Automation When ideally does AHCA want to have this replacement system to “go live”? Please elaborate upon any timing considerations for when specific programs / areas / functions will need to be fully transitioned to the new solution.

As soon as feasible.

33 System Automation Can respondents assume that the portable devices / tablets for AHCA inspection staff and internet connectivity will be supplied by AHCA?

Yes, the devices will be AHCA supplied.

AHCA RFI 025-25/26, ADDENDUM 2, Page 2 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

34 System Automation What costs has AHCA incurred for initial set up of VERSA and annual support (ongoing maintenance, hosting, software licensing, support, and enhancements i.e., “change orders”)?

Versa was implemented about 25 years ago so prices aren't comparable.

35 System Automation What presentations, software demonstrations and/or estimates / quotes have AHCA programs received related to this project and from whom?

This will be done in the RFP phase.

36 System Automation Other than the Versa Oracle database, are there any other sources of data and/or documents to be migrated?

Potentially, depending on the selected solution.

37 System Automation Can AHCA provide any budgetary information at this time? If so:

a. What is AHCA’s budget for the initial system implementation?

b. What, if any, amount of the budget is subject to expire by a certain timeframe and when? Please elaborate.

c. What amount is being budgeted for ongoing support, software licensing, hosting, and support of the new system?

Not at this time.The Agency is looking for competitive pricing.

38 System Automation Does AHCA desire the option for staff to be trained in application administration to make changes, updates, and add new capabilities to the system after go-live? Or is AHCA anticipating that the vendor will perform future updates and changes (such as addition of new license types, form configuration, business rule changes, etc.) to the system?

The Agency is open to all solutions.

39 System Automation Please provide an approximate number of standard email/letter templates that will be used by AHCA that are to be integrated and automated by the system.

The Agency has several hundred currently but will be looking for consolidation opportunities.

40 System Automation How many different or distinct permit and license application types will be supported in this solution? Please provide a comprehensive list.

The Agency have over 30 provider types and at least 4 different application types depending on your exact definition.

41 System Automation Can AHCA identify ALL agency-internal and external systems that the new solution will need to integrate with along with an inventory of which interfaces will need to be whether a one-way (import or export) or two-way data exchange?

It will interact with several dozen other applications and at a minimum the Agency expect API's capable of sending and receiving information and the ability for other applications/databases to extract data from the licensing system.

42 System Automation Please provide the annual number of applications, renewals, and inspections processed by

AHCA.

The Agency has roughly 50,000 application transactions and roughly 22,000 inspections a year.

43 System Automation Given the short timeline between the posting of the Q&A and the response due date, can the response due date be extended by at least 1 week?

Please see Addendum No. 1

44 System Automation Can AHCA provide an inventory of all the reports that need to be replicated within the new system?

No, this will vary based on the selected solution.

45 System Automation pg. 3 The Statement of Need on Page 3 of the RFI indicates that FedRAMP-based solutions are desired. Though our solution is hosted in a FedRAMP environment, our solution, like many others in the state-focused ESI market, is not itself FedRAMPed. Do other industry standard certifications like SOC 2 Type II and GovRAMP also meet AHCA’s information security standards?

FedRAMP is encouraged but not required.

46 System Automation pg. 6 Page 6 of the RFI requests "General Pricing Information". Is it correct to interpret this to mean that AHCA does not yet want pricing estimates, but rather an understanding of the pricing structure and the factors that are considered in price?

Yes.

47 Appian Could you please provide a brief overview of the current technology stack, including information about key legacy systems or applications that will need to integrate with the proposed solution? Are there specific data migration or integration requirements that should be considered?

No, this will vary based on the selected solution.

48 Appian Are there specific business processes or workflows within the agency that are currently experiencing bottlenecks or inefficiencies? If so, could you briefly describe those areas or metrics associated with those (For instance days/hours it would take to process a claim or a case)

The associated metrics vary too greatly to list here. Work distribution and applications processing ease is an inefficiency.

49 Appian What is the estimated number of users expected to interact with the new solution, and what are the anticipated future scalability requirements over the next 3-5 years?

The Agency estimate roughly 400 active users and scalability will vary based on the selected solution.

50 Appian What is the anticipated timeline for implementation of the new solution, and are there any specific milestones or deadlines that must be met for an minimum viable product?

As soon as feasible.

51 Appian What are the IT operations processes you are targeting to transition from manual to automated?

The Agency prefer to not need internal IT staff to maintain the application server.

52 Appian Are you targeting to have online submissions only? To verify, how are current health facility application submissions processed?

Mandating online submissions is a goal, however, legislative changes will be necessary to require this. Currently only renewal applications are required online.

53 Appian How often are updates applied to the technology stack and application? What is the state's expectations for timeframes to apply updates?

Our current application is rarely updated, future updates vary based on the selected solution.

AHCA RFI 025-25/26, ADDENDUM 2, Page 3 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

54 Strategic Communications Does this require FedRAMP Authorized status at time of RFI response, or will FedRAMP Ready / In Process be acceptable for a subsequent procurement?

This is possibly acceptable.

55 Strategic Communications Can they provide a list of the current systems integrated with VERSA that the replacement solution must maintain connectivity with on Day 1?

No, but it's several dozen at least.

56 Coastal Cloud The agency has indicated the purpose of this RFI is to consider replacing an on-prem system with a cloud-based solution. Can you share any other pain points of the current solution that you hope will be solved with the new solution?

Work distribution and applications processing ease would be high priorities.

57 Coastal Cloud We work to provide solutions that accomplish strategic goals while adhering to budget guidelines as much as possible. To better inform our approach, will you please share what the budget allotted for this work is and for which fi scal year(s)?

Not at this time.The Agency is looking for competitive pricing.

58 Coastal Cloud Can you confirm the primary business objectives and success metrics for this initiative? See IV-C of the RFI, but this will vary based on the selected solution.

59 Coastal Cloud How many internal agency users will need full access to the system? The Agency currently have roughly 400 users.

60 Coastal Cloud How many users will need partial access to review / approve applications? Unsure, this may vary based on the selected solution.

61 Coastal Cloud How many licensing applicants will need access to the system? Unsure, but the Agency have over 50,000 providers.

62 Coastal Cloud How many total distinct application types will need to be built?

For each type should we account for an Initial, Renewal, Change of Ownership, and Reinstatement format?

The Agency have over 30 provider types and at least 4 different application types depending on your exact definition.

63 Coastal Cloud How many/what integrations are required, and which systems own the source of truth for each data domain?

The new system will be the source of truth for licensing information, but integrations with other systems will vary based on the selected solution.

64 Coastal Cloud Is API documentation available for all required interfacing systems? Not at this time.

65 Coastal Cloud Do you have requirements for authentication, SSO, MFA, or other security protocols? Not at this time.

66 Coastal Cloud Are there any security requirements the solution will be subject to? Do CJIS requirements apply to the licensing system?

CJIS should not be a requirement but there are confidentiality considerations.

67 Coastal Cloud Can you describe the current state of data quality and any known cleanup or normalization needs?

Data quality is mostly good but the Agency is always looking to make it better.

68 Coastal Cloud How many historical years of data require migration?

Can the Agency provide further technical metadata, such as the approximate number of tables, total record counts for mission-critical entities, and the average number of fields per table?

This will vary based on the selected solution.

69 Coastal Cloud Do you currently have a data lake or Lakehouse environment?

If yes, what platform or technology is it built on (e.g., Snowfl ake, AWS, Azure, GCP)?

Which systems currently send data to the data lake, and how is that data ingested? Who is responsible for managing and maintaining the data lake today?

What analytics, reporting, or downstream systems rely on the data in your data lake?

There is a current data lake that reloads nightly, is managed by internal IT staff and is used for several different report types and applications.

70 Coastal Cloud If this project goes to procurement, what is the anticipated timeline for RFP release and vendor selection?

At this time, the Agency does not have an anticipated timeframe for releasing a solicitation. All formal competitive soliciations will be posted on the Vendor Information Portal.

71 Coastal Cloud Do you have required deadlines or events that impact the timeline or dictate the go-live?

(e.g., fi scal year, peak seasons)?

No.

72 Coastal Cloud What is the readiness level of your user base for adopting new systems? User base is aware a new system is being sought.

73 Coastal Cloud Do you have preferences for training format, materials, or delivery methods? No, The Agency is open to all solutions.

74 Coastal Cloud What level of hypercare or stabilization support do you expect after launch? Will vary based on the selected solution.

75 RedMane Technology LLC VII/ pg. 6-7 “The software used to produce the electronic files must be Microsoft Word 2013 and/or Excel 2013 or newer.” Is it acceptable to provide the electronic redacted copy in PDF format?

Yes.

76 RedMane Technology LLC pg. 4 “Describe how the solution operates in a public sector environment with several audit requirements.” Does the reference of "several audit requirements" refer to technical/security type audits, or more program/operational audits required by federal or state entities?"

All audit types are possible.

77 Salesforce Beyond the 265GB Oracle database migration, does the Agency have existing reports, dashboards, or data extracts from the current VERSA system that must be replicated or replaced in the new solution?

This will vary based on the selected solution.

78 Salesforce What are the primary data consumers of the current VERSA system (e.g., internal staff, executive leadership, other state agencies, the public)? Will each group require different levels of metrics and analytics access?

All those groups are primary users and different levels of metrics will be necessary.

AHCA RFI 025-25/26, ADDENDUM 2, Page 4 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

79 Salesforce The RFI references "customizable reports for tracking key metrics" — can the Agency provide examples of the key metrics it currently tracks or wishes to track (e.g., application volumes, license renewal rates, inspection outcomes, enforcement actions)?

All the examples you listed plus any statutory or regulatory timeframe will be necessary.

80 Salesforce Will the Agency require real-time or near-real-time reporting, or is scheduled/batch reporting sufficient for its operational needs?

This will vary based on the selected solution.

81 Salesforce Does the Agency anticipate the need for self-service analytics, where non-technical staff can build and modify their own reports without IT involvement?

Yes.

82 Salesforce The RFI identifies key data entities including Eligibility, Licenses, Permits, Invoicing, and Payments — does the Agency anticipate needing analytics that span across all of these entities (e.g., cross-domain dashboards correlating license status with payment history)?

Yes.

83 Salesforce As the Agency intends to extend the data model with low-code/no-code applications, does it expect analytics and reporting capabilities to automatically extend to those new data elements without custom development?

Ideally, yes.

84 Salesforce Are there specific statutory or regulatory reporting obligations (e.g., reports to the Florida Legislature, CMS, or federal agencies) that the new system's analytics layer must support?

Yes.

85 Salesforce Does the Agency require audit trail reporting — i.e., the ability to track and report on who accessed, modified, or approved licensing records?

Yes.

86 Salesforce Are there use cases for providing reports and metrics to the public? Yes, please see https://healthfinder.fl.gov/ for examples of publicly provided information.

87 Salesforce Can the Agency clarify expectations around Service-Oriented Architecture (SOA)—specifically whether a modern API-led connectivity approach is preferred to decouple systems and support long-term scalability?

Modern API-led connectivity is preferred, but open to all solutions.

88 Salesforce Can the Agency elaborate on expectations for API connectivity, including API reuse, external partner access, and lifecycle governance?

The Agency will need robust API capabilities to both send and receive data.

89 Salesforce Is there a requirement for a centralized API catalog or marketplace to enable reuse across Agency systems?

No, but that sounds great.

90 Salesforce Can the Agency provide additional detail on integration expectations with Enterprise Data Warehouse, DataMarts, and external systems, particularly around reuse and standardization?

This will vary based on the selected solution.

91 Salesforce How does the Agency envision managing continuous updates (“Evergreen IT”) across integrations—should integration services be independently deployable and versioned?

Updates should minimize application downtime however possible.

92 Salesforce Will the Agency require support for hybrid deployment models (cloud + on-prem / VPC) to meet evolving compliance or operational requirements?

The Agency is open to all solutions.

93 Salesforce Will the Agency require real-time data synchronization between the licensing system and enterprise systems such as EDW and DataMarts?

No, it wouldn't be a requirement, but would be a consideration.

94 Salesforce Does the Agency have a preferred integration approach (e.g., APIs vs batch vs direct database connections)?

APIs are preferred, but the Agency is open to all solutions.

95 Salesforce Does the Agency envision this platform as part of a broader enterprise integration strategy where APIs and integrations are reused across multiple systems and agencies?

The Agency will consolidate APIs wherever possible.

96 Salesforce How does the Agency plan to ensure data consistency and standardization across systems (e.g., licensing, eligibility, payments), and is there a requirement for Master Data Management (MDM)?

Not a requirement, but it is a goal.

97 Salesforce Can the Agency elaborate on expectations for the industry data model, including governance of shared data entities and relationships across applications?

This will vary based on the selected solution.

98 Salesforce What data governance policies are required for handling sensitive health data, including data classification, masking, and auditability?

HIPAA, PHI and PII.

99 Salesforce Is there a need for a unified governance framework that spans APIs, integrations, and data assets across the Agency?

The Agency is open to all solutions.

100 Ondaro What specific modules of the VERSA system are in active use today — licensing, inspections, enforcement, invoicing — and are all modules expected to be replaced in scope?

The application, licensure, cash, enforcement and a customized inspection module are all used.The Agency is open to all solutions when it comes to a replacement.

101 Ondaro Can the Agency provide a data dictionary or entity-relationship diagram for the current Oracle VERSA database to assist vendors in assessing migration complexity?

Not at this time, but internal staff with VERSA database knowledge will assist with migration.

102 Ondaro Are there existing integration points between VERSA and other Agency systems (e.g., Medicaid, FMMIS, or state financial systems) that must be preserved or replicated in the new solution?

The Agency is open to all solutions.

AHCA RFI 025-25/26, ADDENDUM 2, Page 5 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

103 Ondaro What is the volume of active license records, annual application submissions, and inspection records currently managed in VERSA?

The Agency has over 50,000 providers, over 30,000 application submissions and over 20,000 inspections per year managed in Versa.

104 Ondaro Does the Agency expect a parallel-run period between VERSA and the new system, and if so, what is the anticipated duration?

The Agency is open to all solutions.

105 Ondaro Does the Agency require FedRAMP High authorization specifically, or will FedRAMP Moderate be acceptable?

FedRAMP is encouraged but not required.

106 Ondaro Will the solution be required to reside within the Florida state cloud infrastructure or a state-approved cloud environment, or is a vendor-managed GovCloud deployment acceptable?

GovCloud would possibly be acceptable.

107 Ondaro Is there a preference for a specific cloud hyperscaler (AWS, Azure, GCP)? The Agency is open to all solutions.

108 Ondaro Beyond licensing and permitting, does the Agency expect the new solution to fully replace the inspection scheduling and enforcement tracking capabilities currently in

VERSA?

The Agency is open to all solutions.

109 Ondaro Is the Agency's chatbot requirement limited to applicant-facing interactions, or is an internal staff-facing virtual agent also expected?

Both would be optimal, but external preferred.

110 Ondaro Does the Agency anticipate the new system will need to support fee collection and payment processing directly, and if so, is there an existing state payment gateway (e.g., MyFloridaMarketPlace or a similar portal) it must integrate with?

There is an existing gateway (NIC) that the new system will likely need to integrate with.

111 Ondaro Are there specific reporting or analytics requirements beyond operational dashboards — for example, submissions to CMS, federal reporting mandates, or legislative reporting?

This will vary based on the selected solution.

112 Ondaro What are the Agency's primary enterprise systems that will require API integration with the new platform (e.g., ERP, document management, identity/SSO, state data warehouse)?

This will vary based on the selected solution.

113 Ondaro Does the Agency currently use a state-standard identity provider or SSO solution (e.g., Florida Digital Service identity platform) that the new system must federate with?

There is an existing SSO (Okta) but the Agency is open to all solutions.

114 Ondaro What DataMart or Enterprise Data Warehouse systems does the Agency reference in Section IV.D.1, and what data flows are expected between the licensing system and those environments?

There will need to be robust data flow capabilities, both in and out of the chosen system, but the Agency is flexible as to the how.

115 Ondaro Is there an existing API gateway or integration middleware in the Agency's environment that the solution must conform to?

Not currently.

116 Ondaro Does the Agency anticipate issuing a single solicitation covering both the software platform and implementation services, or will these be procured separately?

At this time, the Agency has not developed a procurement strategy.

117 Ondaro Will the Agency consider responses from implementation partners who are not the platform OEM, including pure-play system integrators proposing a named platform (e.g., ServiceNow)?

The Agency welcomes all responses to this RFI.

118 Ondaro Is there a preference or requirement for the prime contractor to hold a Florida state term contract, Alternate Contract Source, or GSA MAS schedule as the vehicle for a future procurement?

No. At this time, the Agency has not developed a procurement strategy.

119 Ondaro Will subcontractor or teaming arrangements be permissible, and does the Agency have any small business or Florida-based vendor participation requirements?

120 Ondaro What is the Agency's anticipated go-live timeline for the replacement system?

As soon as feasible.

121 Ondaro Does the Agency have an internal project management office or dedicated IT team that will actively participate in the implementation, or will the vendor be expected to provide full delivery ownership?

Yes, an AHCA team will be actively participating.

122 Ondaro Are there any legislative or regulatory deadlines driving the replacement timeline that vendors should be aware of?

No.

123 Ondaro Is the Agency open to a subscription-based SaaS pricing model (e.g., per-user or platform tier), or does it require a more traditional perpetual license or transaction-based pricing structure?

The Agency is open to all solutions.

124 Ondaro Should pricing responses reflect implementation, data migration, training, and ongoing managed services as distinct line items, or does the Agency prefer a fully bundled total cost of ownership model?

Distinct line items is preferred.

125 ISF Is AHCA seeking a complete system replacement only, or also modernization of business processes associated with licensing and inspections?

Complete system replacement.

126 ISF Should the solution include inspection scheduling, enforcement workflows, or mobile field inspection tools?

The Agency is open to all solutions.

AHCA RFI 025-25/26, ADDENDUM 2, Page 6 of 7

NO. VENDOR NAME SECTION

IDENTIFIER,

PAGE NUMBER

QUESTION ANSWER

127 ISF Does AHCA anticipate integrating with any additional systems beyond the current VERSA-connected systems? If so, which ones?

Unknown at this time.

128 ISF Is the 265GB Oracle database fully structured data, or does it include documents/attachments?

The Oracle database does not include documents/attachments.

129 ISF Will AHCA provide data mapping documentation or data dictionaries for VERSA? Internal staff with VERSA database knowledge will assist with migration.

130 ISF What is the expected cutover strategy (big‑bang vs. phased)? Big-bang.

131 ISF Is AHCA requiring FEDRAMP High, Moderate, or Low authorization? FedRAMP is encouraged but not required.

132 ISF Does AHCA require vendors to use a specific cloud provider (e.g., Azure Gov, AWS

GovCloud, Google Gov) or is selection open?

The Agency is open to all solutions.

133 ISF What availability, redundancy, and disaster recovery standards are required? These are all considerations,but the Agency is open to all solutions.

134 ISF What existing enterprise systems must the new licensing system exchange data with? The Agency is open to all solutions.

135 ISF Does AHCA currently use an Enterprise Service Bus (ESB), API gateway, or middleware platform?

No.

136 ISF Does AHCA require multilingual applicant support within the online portal? Not required but would be considered.

137 ISF Will the Chatbot need to integrate with an existing state AI/knowledge base? Potentially, depending on the selected solution.

138 ISF Are there specific Florida state security standards in addition to FEDRAMP that must be met (e.g., Florida Cybersecurity Standards)?

Potentially, depending on the selected solution.

139 ISF What identity and access management (IAM) systems does AHCA use today (e.g., Azure AD, Okta)?

Okta implementation is an AHCA goal, but may not be a requirement.

140 ISF Are there specific audit logging retention requirements (HIPAA, CMS, state-level standards)?

Yes.

141 ISF Is AHCA primarily seeking subscription‑based pricing, modular pricing, or cost ranges for planning purposes?

The Agency is open to all solutions.

142 ISF Does AHCA want pricing for implementation only, or also ongoing operations/support? The Agency is open to all solutions.

143 Computronix Has AHCA identified an anticipated budget range or funding approach for a potential future procurement related to this RFI?

Not at this time.

144 Computronix For planning and scalability purposes, approximately how many internal agency users are anticipated to require access to the system at go live and over the next three to five years?

If available, please distinguish between full access users and mobile users.

The Agency currently have roughly 400 users.

145 Computronix What are the primary business, operational, or policy drivers influencing the agency's desired implementation timeframe for a potential future system replacement?

A more modern system with better integration options and automation capabilities.

146 Computronix Are there specific functional areas the agency views as highest priority for modernization in an initial phase?

Work distribution and applications processing ease would be high priorities.

147 Computronix Which departments or roles are expected to participate in the evaluation and recommendation process for any future procurement stemming from tis RFI.

The Agency anticipate staff from multiple divisions, including Health Quality Assurance and Information Technology, will be involved in any future procurement process.

AHCA RFI 025-25/26, ADDENDUM 2, Page 7 of 7