New article
Recently updated
Ideagen Maritime Health 3.0.2 release notes
Who is this article for?
Administrators who are considering implementation of Ideagen Maritime Health 3.0.2.
No elevated access or permissions are required.
This article outlines the changes made to Maritime Health in release 3.0.2, which is available to be scheduled for deployment from 31 August 2026.
Please contact your Ideagen Maritime Health representative for deployment assistance and configuration requirements.
Features
(SC-15989) Updated VSP AGE Log file
The Vessel Sanitation Program (VSP) log file for Acute Gastroenteritis (AGE) generated by Maritime Health has been updated to comply with new requirements provided by the CDC in August 2026. This new template adds a column for Food Worker and has an expiration date of July 31, 2029. In Maritime Health the log file is generated at
- Maritime Health Onboard
- Dashboard
- AGE tab
- Actions
- Download Reportable Log
The value recorded in the new Food Worker column is determined by the selection made on the following field:
- Maritime Health Onboard
- Patient chart
- Select Case, then Encounter
- Public Health
- Create new Public Health entry
- Select Acute Gastroenteritis from type dropdown
- FOOD HANDLER radio button
Fixes
| Number | Description |
|---|---|
| 898237 | Enabled partial refund capability in Otalio interface - a Maritime Health user can now issue a refund for only a portion of the charges originally paid by the client. This change must be verified in a deployed staging/UAT environment to ensure complete integration including application of taxes and fees. |
| 1483552 | Fixed an issue where the Crew Portal failed to sync and display a crew member's SMFC/PEME status after they were checked out from the Maritime Health SMFC/PEME dashboard, causing their status card to remain blank even after submitting or accepting SMFC documents. |
| 1489919 | Fixed an issue where the color palette used in the Scheduler calendar contained color options that were difficult to distinguish from each other, in particular blue and teal. The color palette now provides sufficient contrast between colors. |
| 1491174 | Fixed an issue where beginning a new voyage failed with an internal error message of "Multiple voyages found." |
| 1493702 | Fixed an issue where the patient chart switched to another patient when unlocking an encounter or when attempting to add a new Public Health test and selecting Continue on the "Unposted MSB" prompt. |
| 1496366 | Fixed an issue where retrieving patient data from Otalio led to slowdowns and sync failures. The behavior was caused by multiple authentication requests being made through the Otalio integration across paginated data. The number of authentication requests has been reduced, however complete functionality must be verified in a deployed staging/UAT environment. |
| 1500599 | Fixed an issue where crew members were able to be enrolled in Crew Wellness Programs that were marked as inactive. |
| 1515020 | Fixed an issue where non-SMFC document types in the SMFC/PEME module incorrectly inherited metadata from a previously accepted SMFC document when processed within the same window. |
| N/A | Reverted a prior change to the export report file used in the integration with CARS. The export file originally provided the "Treatment Beyond First Aid Date" field as a Date only but was modified in version 3.0 to provide this field as a Date and Time. In version 3.0.2 this field is reverted to be written as only a Date. Note that in the Maritime Health UI the field is still captured as both Date and Time, but only the Date component is written to the export report. This change must be verified in a deployed staging/UAT environment to ensure the third-party Data Integration tool correctly ingests the export report file. |
Note: Features and fixes listed in this release were tested with Google Chrome 152.0.7977.65 (64-bit) and Microsoft Edge 151.0.4129.107 (64-bit).
While we strive to ensure compatibility, we cannot guarantee functionality with newer browser versions, as third-party updates may introduce changes that affect existing functionality as well as performance. For the best experience, we recommend using the tested versions or contacting support if issues arise with newer releases.