What is ICE?
The Immunization Calculation Engine (ICE) is a free, open-source immunization forecasting software system. The core component of ICE is the ICE Web Service, which evaluates a patient's immunization history and generates the appropriate immunization recommendations for the patient. The ICE Web Service runs in OpenCDS which is a third-party platform that may be used to build decision support services for any clinical domain.
ICE comes initially configured with a default immunization schedule that supports all routine childhood, adolescent, and adult immunizations - based on the recommendations of the Advisory Committee on Immunization Practices (ACIP).
The ICE software system has been developed and configured by a collaborative partnership of public health experts and information technology experts from the organizations listed below and has been released under a standard open-source license:
Due to its standards-based Web Service interface, its Java-based implementation, and its complete lack of dependence on any commercial software, ICE can be deployed in diverse technical environments and easily integrates with third party clinical systems such as Immunization Information Systems (IIS), Electronic Health Record Systems (EHR-S), and Health Information Exchanges (HIEs).
Clinical systems utilize the ICE Web Service by passing a Virtual Medical Record (vMR) to its Web Service which adheres to the Decision Support Service (DSS) standard. In response, ICE utilizes its immunization rules and the data in the vMR, such as the patient’s date of birth, gender, immunization history, and disease indicators, to evaluate and return the validity of each immunization in the patient’s history along with one or more evaluation reasons. It also returns a recommendation for each vaccine group along with one or more recommendation reasons. ICE’s Web Service architecture scales to support simultaneous real-time processing of many patients submitted by one or more systems. It can also service requests for multiple immunization schedules. For example, a single ICE deployment could enforce one immunization schedule utilized by an IIS, another immunization schedule used by multiple EHR-S, and a third immunization schedule utilized by a school health system.
- December 7th, 2022 - New Release of ICE - Version 1.37.1
- ICE Plans for COVID-19 Implementation
- HLN is actively monitoring all news and updates in regards to new and existing COVID-19 vaccines.
- Once a vaccine has been approved for use by FDA (either Expanded Access, EUA, or full licensure), ACIP will hold an emergency meeting and publish recommendations in a very quick timeframe (i.e. days). HLN intends to release a version of ICE that includes COVID-19 forecasting as early as possible after ACIP has published the guidelines. This initial release will contain COVID-19 logic known at the time of the release. As additional, actionable information on COVID-19 forecasting becomes available from official sources, HLN will continue to release additional versions of ICE, at appropriate times to reflect ongoing updates.
- If you have any questions, comments or suggestions, please e-mail us at firstname.lastname@example.org.
- The Importance of Upgrading After Each ICE Release
- With each new release, we strongly recommend that all users and service providers update their running instances of ICE as soon as possible to the latest version. Each new release contains important forecaster business logic updates and bug fixes.
- ICE Code Systems and Codes Now Available in Google Sheets
- The ICE code systems and codes are now accessible in Google Sheets as an added convenience. These are the codes as those in the Implementation Guide. The codes will continue be updated in both the places.
- The Google Sheet is available here.
- Configuration Note
- As of release 1.24.1, the ICE service is configured with the output_supplemental_text option in the properties file set to enabled by default.
- As of release 1.16.1, the ICE service is configured by default to return the earliest and overdue dates in addition to the recommendation date. In prior releases, the default configuration was to return only the recommendation date for the forecast.
- If your application has not been configured to display the earliest and/or overdue dates, we recommend turning this feature off by changing the output_earliest_and_overdue_dates value in the ice.properties file to "N". Failure to do so may result in incorrect interpretation of the recommendation date.
- If you are interested in returning the earliest date or overdue date, please refer to the latest ICE Implementation Guide for details indicating precisely where each of the forecast dates – earliest, recommended, and overdue – are specified in the ICE output, and under what circumstances.
For more information, see the Full List of Archived News...