PHIN Sunset

Overview

By November 30, 2026, PHIN tools will be fully sunset and no longer available. CDC will start the decommissioning process in early November. Users should complete their transition to, or begin using, an alternative solution by November 2, 2026, to ensure continued functionality and support an orderly shutdown of PHIN tools.

CDC will provide the PHIN user community with advance notice of key transition dates and any changes that affect tool availability through multiple forums, including updates on this website.

PHIN functionality remains unchanged at this time. Until otherwise communicated, users may continue to access and use PHIN tools as they do today.

This decision is part of CDC's broader efforts to strengthen and sustain the nation's public health data infrastructure. CDC is working to maintain access to critical functionality currently supported by PHIN through alternative tools and services during and after the transition.

For general questions or concerns about PHIN sunsetting, email OPHDSTPartnerships@cdc.gov with the subject line "PHIN Transition."

PHINMS

Key Function Summary: enable secure, automated exchange of public health data and messages between CDC and public health partners.

• CDC will retire the PHIN Messaging System (PHINMS) by November 30, 2026. To ensure continued, reliable transmission of data, jurisdictions and other partners using PHINMS will need to transition to an approved alternative transport. Users should complete their transition from PHINMS by November 2, 2026, to ensure continued functionality and support an orderly shutdown of PHIN tools as decommissioning activities begin in early November.

• CDC is offering Mercury S3 as the transport solution for sending data to CDC. Mercury S3 is CDC's new secure file transport method that uses Amazon Web Services (AWS) Simple Storage Service (S3) to enable secure, automated data exchange between CDC and public health jurisdictions and partners.

• CDC is also working with the Association of Public Health Laboratories (APHL) to update all connections between the APHL Informatics Messaging Services (AIMS) platform and CDC that have historically relied on PHINMS. This work includes establishing a Mercury S3 connection to support continued data transmission between AIMS and CDC.

• Jurisdictions and partners that use PHINMS to exchange data with organizations other than CDC will need to identify and implement an appropriate alternative secure transport solution. Organizations may wish to consider secure, automated exchange approaches with capabilities similar to those provided by Mercury S3.

Case Notification Data Sent to CDC

For jurisdictions currently sending case notifications directly to CDC using PHINMS, there are two options:

• CDC will work with you to transition using CDC's Mercury S3 service (preferred); OR

• You can consult with APHL on possible AIMS transition options (i.e., using AIMS as an intermediary for sending the case notification data to CDC).

For jurisdictions currently sending notifications to CDC via AIMS, there are two options:

• You can continue sending case notification data to AIMS. Note: If using PHINMS to send to AIMS, you will need to consult with APHL regarding transition options. We are working with APHL to transition from using PHINMS to using Mercury S3 for their connection to CDC; OR

• You can transition from AIMS to a direct-to-CDC Mercury S3 feed. This option is available to interested jurisdictions but is not required. If currently using PHINMS to send to AIMS, CDC will work with you to transition using the Mercury S3 service. For jurisdictions who are not currently using PHINMS but are still interested in establishing a direct connection, CDC can support transitions to Mercury S3 after November 30, 2026.

Benefits of Mercury S3

Mercury S3 is a secure, no-cost, industry-standard transport option that integrates readily with existing systems. It supports both SFTP and API-based transfer, accommodates large file volumes, and supports HL7® and NBS Master Message formats. Mercury S3 has already been successfully adopted by multiple jurisdictions.

Technical Scope

For most jurisdictions, this transition involves a limited technical change, updating where your data are sent and your login credentials to route to Mercury S3. CDC technical staff can assist with this process.

Transition Support

CDC recognizes that transitions of this nature may present challenges for some jurisdictions. Jurisdictions anticipating difficulty with the PHINMS timeline or process are encouraged to contact CDC at edx@cdc.gov with the subject line Mercury S3 transition so that CDC can work with them to identify an appropriate path forward.

CDC values jurisdictions' continued partnership and commitment to timely, high-quality public health data reporting. Please contact CDC at edx@cdc.gov with the subject line Mercury S3 transition with any questions or concerns.

PHIN VADS

Key Function Summary: Provide access to standardized public health code systems and value sets that enable consistent data collection and exchange across public health systems.

• PHIN VADS is currently fully available and expected to be until the beginning of November 2026. Users can access and use it as needed until otherwise notified.

• To prepare for the PHIN VADS sunset, we have evaluated other potential tools to replace the functionality of hosting and distributing content and authoring new content.

• We will systematically migrate PHIN VADS content to other tools to maintain critical functionality, while continuing to explore enhancements beyond the initial transition.

Available Tools and Resources

Below are alternative tools that provide access to code systems and value sets:

• Value Set Authority Center: a freely available tool hosted by the National Library of Medicine for both authoring vocabulary and distributing it for use.
• Cartos: Terminology resource hosted by the Office of the National Coordinator for Health IT (ONC) that provides value sets and code systems for use in data exchange that is referenced in ONC regulations and data standards initiatives.

• HL7 Terminology (THO): Health Level Seven (HL7) supported terminology resource.

• Enterprise Value set Repository (EVR) on the One CDC Data Platform (1CDP): Coming soon, EVR is a repository of value sets and code systems (including all current VADS content) for partners with access to 1CDP to facilitate standardized public health data collection.

Additional web resources for CDC-developed code systems (will update periodically):

• Healthcare Facility Patient Care Location (HSLOC)

• CVX -- Vaccines Administered

• ICD-10-CM

• Occupational Data for Health

• NNDSS Event Codes and Associated PHIN VADS Value Sets

For questions or concerns, please contact OPHDSTPartnerships@cdc.gov with the subject line "PHIN Transition".

PHIN DIR

Key Function Summary: provide a centralized directory of public health organizations, facilities, and contacts to support data exchange across the public health community.

• Please continue to request new OIDS or OID information through the PHIN help desk at PHINTech@cdc.gov.

• Check this page for updates.

Disclaimer

HL7^® is a registered trademark of Health Level Seven International and use of this trademark does not constitute an endorsement by HL7.