Case Notification for Tuberculosis v2.0
Case Notification Standards for Tuberculosis and Guidelines for Implementation
There are currently 3 case notification standards for TB: the NETSS.dat format, PHIN Case Notification Guide for Tuberculosis Version 1.0, and PHIN Case Notification Guide for Tuberculosis Version 2.0. The following table defines how the standards may be applied to meet CDC recommendations for Tuberculosis case notification.
|Standard||Description||Application for Case Notification|
|NETSS.dat file||NETSS is the legacy standard that is currently in use for transmission of both individual case and summary case reports. TB Reporting jurisdictions may continue to send only new and updated case notifications using the TIMS system for TB cases reported 12/31/2008 and prior. For cases reported 1/1/2009 and following, the PHIN Case Notification Guide for Tuberculosis is the desired standard for case notification to CDC.||For Individual-level Case Reports:
|PHIN Case Notification Guide
Tuberculosis Version 1.0
|Version 1.0 of the PHIN Case Notification Guide for Tuberculosis was published in 2008 and applies to individual-level case reports only. Reporting Jurisdictions may use this version to satisfy case notification recommendations until 12/31/2009. The CDC Program anticipates, by the end of 2010, that reporting jurisdictions have transitioned to the desired message mapping guide version 2.0 for Tuberculosis. Any jurisdictions engaging in HL7 messaging for Tuberculosis after 12/31/2008 is requested to utilize the version 2.0 standard.||For Individual-level Case Reports:
|PHIN Case Notification Guide
|Version 2.0 of the PHIN Case Notification Guide for Tuberculosis was published in 2009 and applies to individual-level case reports only. Reporting Jurisdictions may use this version to satisfy case notification recommendations until such time as surveillance needs require the guide to be updated.* Any jurisdictions engaging in HL7 messaging for Tuberculosis after 12/31/2008 is requested to utilize the version 2.0 standard.||For Individual-level Case Reports Only:
|*Versions of PHIN Case Notification Guides for any Nationally Notifiable Condition (NNC) may change as surveillance needs require, but not more frequently than annually. After a guide is changed, reporting jurisdictions will be given ample time to transition to a newer version (as defined by CDC and reporting partners). Examples of circumstances that may require changes to a case notification guide include, but are not limited to the following: a new or emerging condition, changes in variables or notification criteria voted on at the annual Council of State and Territorial Epidemiologists (CSTE) meeting, change in reporting jurisdiction or CDC program needs, etc.|
CDC is dedicated to working with state partners to transition to HL7 v2.5 messaging for submitting case notifications. CDC will guide state partners through the HL7 v2.5 case notification process to ensure the HL7 structure and message content are validated before moving to production.
Before you begin the HL7 implementation process, please contact CDC by sending an email to PHINtech@cdc.gov. The subject of the email should be, "HL7 Case Notification," and be sure to indicate which message mapping guide(s) you will implement.
|Download these documents to get started:||Download|
|Case Notification HL7 Implementation Checklist|
|Case Notification HL7 Implementation Checklist for NBS states|
|PHIN-MS and SDN Instructions|
|Tuberculosis Case Notification MMG v2.03|
|Tuberculosis v2.0 Test Case Scenarios|
|2009 RVCT form mapped to PHIN variables|
|PHIN Notification Message Specification Profile v 2.0|
|Transmit Condition Report Message Use Case (referenced in the above document)||Coming Soon|