Vital Records Death Reporting (VRDR) FHIR Implementation Guide
3.0.0 - STU3 United States of America flag

Vital Records Death Reporting (VRDR) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/vrdr/ and changes regularly. See the Directory of published versions

ValueSet: Event Code for Death Certificate Composition

Official URL: http://hl7.org/fhir/us/vrdr/ValueSet/vrdr-death-certification-event-vs Version: 3.0.0
Active as of 2025-01-10 Computable Name: DeathCertificationEventVS
Other Identifiers: OID:2.16.840.1.113883.4.642.40.10.48.7

Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement

The code used for Event.code for the Death Certificate Composition

References

Changes since version true:

  • New Content
  • Logical Definition (CLD)

    Generated Narrative: ValueSet vrdr-death-certification-event-vs

     

    Expansion

    Generated Narrative: ValueSet

    Expansion based on SNOMED CT 731000124108 edition 01-Sep 2024

    This value set contains 1 concepts

    CodeSystemDisplay
      307930005http://snomed.info/sctDeath certificate

    Explanation of the columns that may appear on this page:

    Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
    System The source of the definition of the code (when the value set draws in codes defined elsewhere)
    Code The code (used as the code in the resource instance)
    Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
    Definition An explanation of the meaning of the concept
    Comments Additional notes about how to use the code