Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33745

Each return path could be specified in the appropriate FHIR section

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Vital Records Death Reporting (VRDR) (FHIR)
    • 1.2.0 [deprecated]
    • Public Health
    • (many)
    • Hide

      Messaging behavior was addressed in an NCHS-published Vital Records FHIR Messaging IG. VRDR only addresses data content.

      Show
      Messaging behavior was addressed in an NCHS-published Vital Records FHIR Messaging IG. VRDR only addresses data content.
    • Robert Passas/Saul Kravitz : 25-0-0

    Description

      The ballot comment is submitted on behalf of Jeff Greenland, Senior Developer Advocate, NAPHSIS. JGreenland@Naphsis.org

      A coding return path would be helpful so that the receiving system performing coding would know where to send an API notification when complete. Each return path could be specified in the appropriate FHIR section (such as the VRDR-Cause-of-Death-Pathway element for the cause of death coding). This could apply to:

      • Cause of death coding
      • Race tabulation coding
      • Ethnicity coding

      Attachments

        Activity

          People

            Unassigned Unassigned
            Jcouse Jenny Couse
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: