Skip directly to search Skip directly to A to Z list Skip directly to navigation Skip directly to page options Skip directly to site content

METS Release Notes

Version 2.7.4.1 - 05/10/2019
  • Change Request 154: For Babesiosis messages, "Date of Previous Illness" (LOINC code 82758-4) will no longer be a "may
    repeat" data element, that is, repetitions in OBX-5 are no longer allowed. Instead it will be transmitted in a repeating
    group consisting of only the single data element.
Version 2.7.4 - 05/03/2019
  • CR Change Request 150: Babesiosis data elements "Blood Transfusion Date" (14687-8) and "Blood Donation
    Date" (82756-8) are no longer processed as "may repeat" (multi-select) data elements. They are now treated as single
    element repeating groups.
  • Change Request 138:
    • For both Babesiosis and Malaria messages, "Type of Complications" (67187-5) has changed to a stand-alone
      data element for which OBX-5 may repeat (multi-select)
    • For Babesiosis messages, "Treatment Drugs" (55753-8) has changed to a stand-alone data element for which
      OBX-5 may repeat (multi-select).
  • Change: Errors and warnings were not being recorded in the database or displayed in the dashboard for some
    messages which were missing multiple required fields. This is now fixed.
  • Change: Respiratory and Invasive Bacterial Disease (RIBD) messages are now routed to the APHL Informatics
    Messaging Services platform (AIMS). MVPS has routed Foodborne and Diarrheal Disease (FDD) messages to AIMS
    since release 2.5.8.
  • Change: FDD and RIBD messages are now conditionally forwarded to AIMS based on the reporting jurisdiction. This
    allows the forwarding of messages only from states which participate in the Emerging Infections Programs (EIP) /
    Active Bacterial Core (ABC) surveillance program.
Version 2.7.0 - 03/14/2019
  • Change: HAI MDRO (Healthcare-associated infections; Multi-drug resistant organisms) message processing is now supported in MVPS and METS
  • Change Request 144: Listeriosis (event code 10640) messages can now be sent with a Gen v2 message profile
Version 2.6.6 - 02/14/2019
  • Measles message processing is now supported in MVPS and METS
  • Lyme/TBRD (Tickborne Rickettsial Diseases) message processing is now supported in MVPS and METS
  • Change Request 133: PHVS_LabTestType_TB value set upgraded to version 3
  • Change Request 142: TB/LTBI value set change and updates:
    • TB/LTBI data element INV1167 (Final Disease Outcome) vocabulary validation changed to use
      PHVS_YesNoUnknown_CDC value set (previously using PHVS_FinalTreatmentOutcome_TB)
    • PHVS_EpidemiologicalRiskFactors_TB value set upgraded to version 5
    • PHVS_ReasonNotTreatedwithRIPE_TB value set upgraded to version 3
  • Change:METS now performs all vocabulary validation using database values instead of web services. This fixes an issue with legacy message validation
  • Change:A pid_11_9 column has been added to the dot.netss_case_data_extended_hl7_vw view. The HL7 PID-
    11.9 component is the Patient Address County/Parish Code.
Version 2.6.5 - 01/24/2019
  • Change Request 117 - Upgrade to the latest version of the PHVS_Complications_Mumps value set
  • Change Request 120 - Upgrade to the latest version of 3 value sets used with FDD/FoodNet: PHVS_TestMethod_FDD, PHVS_Organism_FDD, and PHVS_OAntigen_FDD
  • Change Request 124 - 'PulseNet Cluster Code' (FDD_Q_1122) replaces 'PulseNet ID' (FDD_Q_1140) for FDD Cholera/Vibriosis
  • Change Request 127 - Changed the value set used for validation of the FDD/STEC FDD_Q_1000 data element from PHVS_YesNoUnknown_CDC to PHVS_YesNoDon'tKnowMaybe_FDD
  • Change Request 130 - Upgrade to the latest version of 4 value sets used for FDD validation: PHVS_Organism_FDD, PHVS_VibrioSpecies_FDD, PHVS_SeafoodType_FDD, and PHVS_TestResult_FDD
  • Change Request 131 - Change the cardinality to multi-select (May Repeat = 'Y') for the following 3 FDD data elements:
    • Travel State (82754-3) - Salmonellosis
    • International Destination of Recent Travel (82764-2) - Salmonellosis
    • Event Date (FDD_Q_186) - Cyclosporiasis
  • Change: Accept the following data element in FDD Cholera/Vibriosis messages:
    • Consumed Medications To Block Acids, Within 30 Days Before Illness (FDD_Q_1029)
  • Change Request 132 - Change the identifiers for 3 FDD/Cyclosporiasis data elements:
    • Store State - Previously INV1274; changed to INV1281
    • Restaurant or Location City Where Exposure Occurred - Previously INV1275; changed to INV1282
    • Restaurant or Location State Where Exposure Occurred - Previously INV1276; changed to INV1283
  • Change Request 135 - Upgrade to the latest version of the PHVS_CaseTransmissionMode_NND value set
  • Change: For STD data elements INV291 and STD123, incorrect value sets were used for validation in addition to the correct value sets. This has been corrected
Version 2.6.4 - 01/10/2019
  • Change: Rubella message processing is now supported in MVPS and METS
  • Change: Congenital Rubella Syndrome (CRS) message processing is now supported in MVPS and METS
  • Change Request 121 - Identifier for 'Vaccine Administered Date' changed from VAC103 to LOINC code 30952-6 for FDD Cholera/Vibriosis
  • Change Request 122 - 'Date Of Onset - Reported' (76425-8) is no longer a valid data element for FDD FoodNet and Campylobacteriosis
  • Change Request 129 - 2019 Event Code changes:
    • New code 50265 - Salmonellosis (excluding S. Typhi infection and S. Paratyphi infection)
    • New code 50266 - Salmonella entericaserotypes Paratyphi A, B (tartrate negative) and C (S. Paratyphi) infection
    • New code 50267 - Salmonella enterica serotype Typhi (S.Typhi) infection)
    • For existing code 11565, event name changed to "Yersiniosis (non-pestis)"
Version 2.6.3 - 12/14/2018
  • Change: Updated METS landing page to show complete list of supported specifications
Version 2.6.2 - 11/14/2018
  • Trichinellosis message processing is now supported in MVPS and METS
  • CR 119: Update to the latest versions of these food exposure value sets used for FDD/Cyclosporiasis processing:
  • Change Request 123: New data elements and value set changes for FDD/Cyclosporiasis
  • Change: In METS, message validation (structural, vocabulary, and business rule) for legacy specifications supported by MQF
  • Fix: Issue a structural error for any OBR-11 value which has a length greater than 1
  • Fix: Empty OBX-1 (Set ID) fields are now identified as structural errors
  • Fix: OBX-3.1 values which contain white space are now processed correctly and flagged with a warning
  • Fix: Processing of some PHLIP messages failed during the writing of the NTE-4.14 value to the database
Version 2.6.1 - 10/09/2018
  • Change: Support for Babesiosis case notification messages
  • Change Request 98: Upgrade to the latest version of the County (PHVS_County_FIPS_6-4) value set.Here is the value set in PHIN VADS
  • Change Request 114: For Tuberculosis and LTBI messages, 3 data elements are added and one data element is removed.
  • Added:
    • INV1276 - Usual Occupation and Industry
    • INV1274 - Case Meets Binational Reporting Criteria
    • INV1275 - Patient Treated as MDR Case
    Removed:
    • INV1138 - Initial Drug Regimen Using RIPE/HRZE
  • Change Request 115: The first component of the HL7 CX datatype has been expanded from a length of 15 to 199. This change affects OBX-5.1 when OBX-2 = 'CX', NK1-12.1, and PID-3.1. Related database changes are described in section 2.2.
  • Change Request 116: For Tuberculosis and LTBI messages, moved the 'History of Previous Illness' data element out of the 'RVCT Previous Disease Repeating Group'. The data element has identifier 161413004 (SCT) and is still valid as a standalone TB/LTBI data element.
  • Fix: In rare circumstances, an error stating that "the combination of the data element identifier (OBX-3) and the observation sub id (OBX-4) must be unique" was generated incorrectly. This has been fixed.
  • Fix: Updated TB value sets to current versions available from PHIN VADS.
Version 2.6.0 - 09/14/2018
  • Change: Processing support for RIBD (Respiratory and Invasive Bacterial Disease) messages.
  • Change Request 108: Added LAB718 (Performing Laboratory Identification Number) data element to the FDD FoodNet Lab Interpretative Diagnostic Questions repeating group.
  • Change Request 109: Made OBX-4 (Observation Sub-ID) optional for the 82754-3 (Travel State) FDD data element.
  • Change Request 107: Added the PHVS_PregnancyOutcome_Listeria value set used for the FDD FoodNet 'Pregnancy Outcome' data element.
  • Change: Increased the maximum size of PID-3.1 from 15 to 199. This is a change to the allowable size for senders and also a database alteration to the size of the pid_3_1 column in the pid_segment tables and the hl7.pid_segment_vw view.
  • Change: Process and provision all data sent in an NK1 segment regardless of the value of the 'Relationship' (NK1-3) field. NK1 (next of kin) data is accessed via the hl7.nk1_segment_vw and hl7.nk1_35_vw views. In previous releases, NK1 data was only stored if the relationship value was 'MTH'.
Version 2.5.8 - 08/29/2018
  • Change Request 90: Addition of 6 condition codes - of the six, only Yersiniosis/11565 is currently reportable.
  • Change Request 93: Updated the PHVS_TestResult_FDD value set.
  • Change Request 99: Removed FDD_Q_1028 and FDD_Q_955 data elements from FDD Cholera/Vibriosis.
  • Change Request 100: Value set changes for FDD Typhoid/Paratyphoid.
  • Change Request 102: Support ETEC (Enterotoxigenic Escherichia coli) as an FDD FoodNet condition.
  • Change Request 103: Added 3 data elements to the FoodNet tab of the FDD MMG: Census tract (PID-11.10), Performing Laboratory Name, and Homeless.
  • Change Request 104: Removed the FDD_Q_33 (Animal Contact Location) data element from FDD Cryptosporidiosis.
  • Change Request 106: FDD data element change - harmonization of two similar "Subject's Outcome" data elements resulting in the replacement of FDD_Q_962 in the Typhoid/Paratyphoid tab which is now reported as FDD_Q_1038.
  • Change Request 107: Changed value set associated with the FDD Pregnancy Outcome data element.
  • Change: Updated the internal condition code table to align with the latest event code spreadsheet.
  • Change: Changed display message for the "unexpected data element" warning.
Version 2.5.7 - 07/12/2018
  • Change: Support for TB/LTBI (Tuberculosis and Latent TB Infection) case notification messages.
  • Change Request 87: Add support for these 3 RIBD condition codes:
    • Streptococcal disease, invasive, group A (Streptococcus pyogenes).
    • Streptococcal disease, invasive, group B (Streptococcus agalactiae).
    • Neonatal sepsis.
  • Change: Update condition codes to align with the latest CDC event code list.
  • Change: Add the PHVS_GeneralConditionStatus_TB value set.
  • Change: Update TB/LTBI (Tuberculosis and Latent TB Infection) condition attributes (category, program, and name).
Version 2.5.6 - 06/17/2018
  • Change: Support for FDD (Foodborne and Diarrheal Disease) case notification messages.
  • Change Request 88: Remove Antimicrobial Susceptibility tab in FDD and use Susceptibility Block instead.
Version 2.5.5 - 06/07/2018
  • Change Request 81: Change value set for Pertussis data elements INV903 and PRT075.
  • Fix: When INV290 data element has empty OBX-5, no location provided.
  • Change Request 86: Implemented Pertussis MMG changes:
    • Changed the code for 'Case Patient a Healthcare Worker' from INV926 to 223366009 (SCT). This aligns with the same data element in Varicella.
    • Changed the name for data element 18185-9 from 'Gestational Age in Weeks' to 'Gestational Age'.
  • Change: Updated value sets used to validate SPM-4 Specimen Type and SPM-8 Specimen Source Site.
  • Fix: METS not displaying some character combinations correctly on the validation page.
  • Change Request 85: Updates based on the latest official version of the PHIN Messaging Specification for Case Notification:
    • Changed the length of PID-32 to 20.
    • Changed the length of NK1-10 to 60.
    • Changed the length of OBR-13 to 199.
Version 2.5.4 - 05/17/2018
  • Change: Throw structural error if SPM-12.1 is longer than 16 characters.
  • Fix: Delete incorrect condition codes.
  • Fix: Incorrect warning when INV290 is absent and no child data elements are present.
  • Fix: No warning when both parents of repeating group are missing.
  • Change: Required update for METS analytics code.
  • Change: Updated list of supported profiles on the METS landing page.
  • Fix: Issue with ELR link on METS landing page.
  • Change Request 82: For the Varicella Specimen Source data element, replace the Varicella-specific value set (PHVS_PCRSpecimenSource_VZ) with the VPD value set (SpecimenTypeVPD) which is already used for Mumps and Pertussis.
  • Change Request 83: Update value set for Mumps/Pertussis/Varicella Vaccine Event Information Source data element.
  • Change Request 84: Add value "other" to the Body Region(s) of Rash (PHVS_BodyRegionOfRash_VZ) and Character of Lesions (PHVS_CharacterofLesions_VZ) value sets for Varicella.
Version 2.5.2 - 04/23/2018
  • Change: Support for Malaria HL7 messages.
  • Change: Accept the lab template in Gen v2 messages.
  • Change: Support for 3 new Gen v2 conditions: Histoplasmosis, Acute flaccid myelitis, and Tetanus.
Version 2.5.0 - 03/29/2018
  • Change: For PHLIP messages, warn if OBX-2, OBX-5, or OBX-8 is populated when OBX-11 = 'X'.
  • Change: For PHLIP messages, allow "0000" in OBR-7 to indicate that the collection date/time is unknown.
Version 2.4.12 - 03/20/2018
  • Change: Support for Varicella HL7 messages.
Version 2.4.11 - 03/09/2018
  • Change: Support for Pertussis HL7 messages.
Version 2.4.10 - 03/01/2018
  • Change: Support for Mumps HL7 messages.
Version 2.4.5 - 01/05/2018
  • Change: Support for STD and Congenital Syphilis HL7 messages.
Version 2.4.1 - 11/20/2017
  • Change: Initial release of METS on upgraded architecture.
  • Change: Some warning and error messages may be worded differently.
  • Change: Two message locations and values are now supported for those errors or warnings which reference two fields.
Version 2.3.3 - 06/05/2017
  • Change: Support New York City jurisdiction as sender of Generic v2 and Hepatitis messages.
  • Fix: Allow "0000" as a valid value for OBR-7 (Observation Date/Time) in PHLIP VPD messages.
  • Change: Simplified the METS application URL.
Version 2.3.2 - 05/03/2017
  • Change: Minor METS UI improvements.
  • Fix: Always issue an error when a required data element is populated with an invalid value (a value not found in the value set).
  • Fix: OBX-1 (Set ID) values must be unique and sequential under each OBR segment.
  • Change: Issue a more detailed error message when MMWR Year or MMWR Week is populated with an invalid value.
  • Fix: Issue an error when NOT118 (OBR-25 - Notification Result Status) is populated with an invalid value.
  • Fix: Issue a warning when PID-11.9 (County/Parish Code) is populated with an invalid value.
  • Fix: Corrected the error message issued when the required data element Case Class Status Code is missing.
  • Change: Recognize 3 new Generic v2 conditions:
    • Condition code 50225, Acanthamoeba disease (excluding keratitis).
    • Condition code 50226, Balamuthia mandrillaris disease.
    • Condition code 50227, Naegleria fowleri causing Primary Amebic Meningoencephalitis.
Version 2.3 - 03/31/2017
  • Change: METS user interface modifications including fixed-width font for message body display.
  • Change: Updates to condition names.
  • Change: Stricter validation of fields OBR-7 (Date First Electronically Submitted) and OBR-22 (Date of Electronic Case Notification to CDC).
Version 2.2.4.2 - 02/28/2017
  • Change: New METS user interface.
  • Change: Accept Trichinellosis, Malaria and Cyclosporiasis as Generic v2 conditions.
  • Fix: Eliminated incorrect warnings generated when PID-7 (Date/Time of Birth) has a value of "99999999".
  • Fix: Corrected the message displayed when OBX-4 (Observation Sub-ID) is not populated for data elements in a repeating group.
  • Fix: Eliminated an incorrect warning message generated when the ninth component of PID-11 is not provided.
Version 2.2.4 - 02/10/2017
  • Fix: Show correct display message when OBX-4 is missing for repeating groups.
  • Fix: Perform content validation on PID-11.4 and PID-11.9.
  • Fix: Show correct display message for Reporting State (77966-0).
  • Fix: Show error for blank MMWR year and week.
  • Fix: Validate value for OBX-3.2.
  • Change: OBX-3 and OBX-4 must be a unique combination for each segment.
Version 2.2.3 - 01/20/2017
  • Fix: Issue an error if MMWR Year or MMWR Week are not populated with a numeric value.
  • Change: Remove limit on number of repetitions for repeating groups.
  • Change: Remove the parent-child relationship for the exposure setting repeating group.
  • Change: For INV134 (Duration of Hospital Stay in Days), issue a warning if OBX-6 (Units) has a value other than "days".
Version 2.2.2 - 01/03/2017
  • Change: MMWR Year value can now be the current year, any prior year, or the next year if the message is processed on December 31.
  • Change: Provide more descriptive error messages when observation values exceed the allowed length.
  • Change: Business rules updated for Generic v2 and Hepatitis messages.
  • Fix: Eliminate incorrect vocabulary warnings related to State and County of Exposure.
  • Fix: Issue warning when OBX-5.1 of INV502/77984-3 (Country of Exposure) is null.
  • User interface fix: Eliminate secure content pop-up displayed by the browser.
Version 2.2.1 - 12/09/2016
  • Change: Validate MSH-21 (Message Profile Identifier) based on the latest PHIN Messaging Guide for Case Notification and issue an error if it is invalid.
Version 2.2.0 - 11/21/2016
  • Change: For any data element in a repeating group, issue an error if OBX-4 is not populated.
  • Change: If a required data element (where CDC Priority or HL7 Usage is "R") is missing or not populated, issue an HL7 structural error.
  • Change: If a required data element contains an invalid value, issue a content validation error.
  • Change: Only accept OBR-4 values that are specified in a supported Message Mapping Guide. Issue an error if an unsupported OBR-4 value is provided.
  • Fix: Do not issue an error for a missing INV2002 (age units) value unless INV2001 (age) is provided.
Version 2.1.7 - 10/31/2016
  • Fix: METS validation and business rules synchronized with MVPS.
  • Change: Warning issued when Hospitalized is NULL and Admission Date or Discharge Date is given.
Version 2.1.5 - 09/16/2016
  • Fix: Warning issued when (LAB115) OBX-6=111 (Invalid) in Hepatitis.
  • Fix: Warning issued when OBX-3.1 =VAC126 and OBX-5 =123 (Invalid) in Hepatitis.
  • Fix: Warning issued when OBX-3.1 =VAC143 and OBX-5 =123 (Invalid) in Hepatitis.
  • Fix: Cosmetic issues.
  • Fix: System no longer displays false warning when valid PHC1274 code was entered for Case Disease Imported Code (INV152) in Gen v2.
  • Fix: Report appropriate errors when required fields (Case Class Status Code, National Reporting Jurisdiction, MMWR Week, MMWR Year) are missing.
  • Fix: Warnings issued in METS or MVPS when Illness End Date (INV138) is not NULL and is earlier than INV137 or DEM115 is invalid in Gen v2.
  • Change: Show warning: "Report Status must be either 'C' or 'F' or 'X' " when NOT118 (Notification Result Status) is not populated with a valid value in Gen v2.
Version 2.1.4 - 08/12/2016
  • Fix: No longer issue a warning about missing primary observation when data element with LOINC code 1920-8 is received in a Hepatitis message.
  • Fix: Warn when Diagnosis Date is earlier than Patient Date of Birth.
  • Fix: Issue an error when Condition Code is missing.
  • Fix: Issue a warning when Hospitalized is indicated but "Duration of Hospital Stay in days" has not been provided.
  • Fix: Issue a warning when Hospitalized is not indicated but "Duration of Hospital Stay in days" is populated.
  • Fix: Issue an error when INV2001 (Age at case investigation) is populated but INV2002 (Age unit at case investigation) is not populated.
  • Fix: Issue a warning when Deceased Date is earlier than Patient Date of Birth.
  • Fix: Issue a warning when Case Investigation Start Date is earlier than Patient Date of Birth.
  • Fix: No longer issue duplicate warning messages when an invalid value is provided for Subject Died (INV145).
Version 2.1.3 - 07/22/2016
  • Change: Added support for Hepatitis E condition.
Version 2.1.2 - 06/28/2016
  • Change: No message validation changes.
Version 2.1.1 - 06/11/2016
  • Change: Standard codes are now discovered and processed in the second triplet of OBX-3 in the case where local codes are provided in the first triplet.
Version 2.1.0 - 06/06/2016
  • Change: Closer alignment of validations to message profile.
Version 2.0.12 - 05/24/2016
  • No message validation changes.
Version 2.0.11 - 05/09/2016
  • Change: Business rule warning and error links in the METS Message Validation page now link to the correct location.
Version 2.0.10 - 04/27/2016
  • Fix: Warning message "Discharge date has been provided but Hospitalized is not indicated" will no longer be displayed when it is not valid.
  • Fix: Warning message "Deceased Date is given but Patient Death from Condition is not set to 'Yes'" will no longer be displayed when it is not valid.
  • Fix: Lab Template - corrected LAB197 to LAB108.
  • Change: Allow PHIN variables INV136 and INV178 instead of the corresponding LOINC codes.
  • Change: An error is generated when a message contains a message profile and a condition code that are not consistent, for example, a Generic v2 message profile with a condition code that is not in the Generic v2 condition code list.
Version 2.0.9 - 04/19/2016
  • Addition: Error for non-notifiable conditions.
  • Change: Updates to the 2016 Event Code List.
Version 2.0.8 - 04/07/2016
  • Addition: Error for a message with MSH-3, MSH-5, or MSH-6 missing.
  • Fix: Type in GenV2 MMG for DEM163 (Subject Address Zip Code) - "O" to "RE".
Version 2.0.7 - 03/02/2016
  • Change: The allowable length of CWE, CE, and SN Data Types has been increased to 199 in order
    to accomodate the use of OIDs as identifiers.
  • Change: PID-7 Date/Time of Birth, if populated, must conform to timestamp format but should not error if
    the year (YYYY) or year and month (YYYYMM) or year, month, and day (YYYYMMDD) are provided and valid.
Version 2.0.6 - 02/15/2016
  • Change: Updated METS Interface with new landing page, left navigation, and message validation page.
  • Fix: Allow full timestamp in OBR-22.
Top