or rescinded. To update information on a previously submitted case, update the information in your surveillance system and re-send the case. Set the Notification Result Status (in OBR-25) to to indicate a “C” correction and, if needed, update the case classification status (e.g., confirmed, probable, suspected, not a case.) The updated record will supersede the previous notification. Be careful not to change data elements used to define a unique case (see or you will cause a new case to be added to the CDC data base instead of updating a previously reported case. If you determine that a previously sent case should not be counted as a case, send an updated case notification using one of the following methods: Preferred Method: Re-send the case with case classification status data element a ‘77990-0’ =“Not Case” and Notification Result Status = to indicate this is a “C” correction. Alternate Method: Re-send the case with case classification status data element = a ‘77990-0’ “Not and Notification Result Status Case” (OBR-25) = to indicate this case “X” is “rescinded”. Alternate Method for jurisdictions unable to send case classification status of a “Not Regardless of the value Case”: transmitted in the case classification status, re-send the case with Notification Result Status (in OBR-25) = to indicate this case is “X” rescinded. 44 Table 5.2.5 OBX-4 Updated the wording in the If the OBX Condition Predicate: condition predicate to help segment is allowed to repeat more than once within the same OBR clarify the usage when segment and contain the same repeating segments. values. 45 Table 5.2.5 OBX-4 Added conformance CONFORMANCE STATEMENT statement to indicate the OBX-4 SHALL have the same requirement for OBX-4 to unique numeric value in each
or rescinded. To update information on a previously submitted case, update the information in your surveillance system and re-send the case. Set the Notification Result Status (in OBR-25) to “C” to indicate a correction and, if needed, update the case classification status (e.g., confirmed, probable, suspected, not a case.) The updated record will supersede the previous notification. Be careful not to change data elements used to define a unique case (see or you will cause a new case to be added to the CDC data base instead of updating a previously reported case. If you determine that a previously sent case should not be counted as a case, send an updated case notification using one of the following methods: Preferred Method: Re-send the case with case classification status data element ‘77990-0’ =“Not a Case” and Notification Result Status = “C” to indicate this is a correction. Alternate Method: Re-send the case with case classification status data element ‘77990-0’ = “Not a Case” and Notification Result Status (OBR-25) = “X” to indicate this case is “rescinded”. Alternate Method for jurisdictions unable to send case classification status of “Not a Case”: Regardless of the value transmitted in the case classification status, re-send the case with Notification Result Status (in OBR-25) = “X” to indicate this case is rescinded. 44 Table 5.2.5 OBX-4 Updated the wording in the condition predicate to help clarify the usage when repeating segments. Condition Predicate: If the OBX segment is allowed to repeat more than once within the same OBR segment and contain the same values. 45 Table 5.2.5 OBX-4 Added conformance statement to indicate the requirement for OBX-4 to CONFORMANCE STATEMENT OBX-4 SHALL have the same unique numeric value in each
PHIN_Messaging_Specification_for_Case_Notification_v3%200_Release_2_2_20180401.docx