Vital Records FHIR Messaging (VRFM) IG
2.0.0-Preview4 - ci-build

Vital Records FHIR Messaging (VRFM) IG, published by CDC NCHS. This guide is not an authorized publication; it is the continuous build for version 2.0.0-Preview4 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/nightingaleproject/vital_records_fhir_messaging_ig/ and changes regularly. See the Directory of published versions

Change Log

Version 2.0.0

  • Eliminated direct dependency on content (BFDR, VRDR) IGs.
  • Added support for Birth, Fetal Death, and Industry/Occupation exchange. Support for death records should be fully backwards compatible.
  • Added payload version parameter to MessageParameters to support messages from all known versions of vital records IGs.
  • Enhanced AcknowledgementMessage to include optional content warnings.

Version 1.0.1

  • Simplified examples of VRDR data used by the VRFM IG. These were a constant battle to maintain as the IG publisher's validation process evolved. The examples have been stripped down to the absolute minimum. No changes should have occured to the technical content of this IG, only to the VRDR-based examples used to illustrate the exchange of content.
  • Changed the dependency on VRDR to the current version to work around IG Publisher issues.

    Version 1.0.0

  • Changed version number to 1.0 to reflect the maturity and stability of the content of this Implementation Guide and its production use. No material changes were made between versions 0.9.1 and 1.0.0.
  • Added further clarification for logical checks in the NCHS business rules regarding injury incident fields.

    Changes prior to 1.0.0

  • Incorporated NCHS business rules for death record submissions.
  • Added note regarding lack of support for extraction error messages by NCHS API (November 2022)
  • Added Alias Message based on input from Veronique, Krynn, and Aaina in February 2021
  • Changed canonical URL to http://cdc.gov/nchs/nvss/fhir/vital-records-messaging
  • All messages use the same basic parameter structure. Not sure this was the case previously.
  • Added Status Message to (initially) report back that a deathrecord will be manually coded.