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

Make Record Identifiers COnsistent between BFDR and VRDR

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Birth and Fetal Death Reporting (FHIR)
    • 2.0.0-ballot
    • Public Health
    • Bundle - Coded Cause of Fetal Death - not named
      Bundle - Coded Race and Ethnicity - Baby G Quinn
      Bundle - Demographic Coded Content Bundle for BFDR
      Bundle - Document Birth and Fetal Death
      Bundle - Provider Live Birth - Baby G Quinn
      Composition - Coded Cause of Fetal Death
      Composition - Coded Race and Ethnicity
      Composition - Jurisdiction Live Birth Report
    • Hide

      The record identifiers have been moved to the Bundle Level for BFDR to be consistent with VRDR and FHIR practice (ID requried on Bundle, optional on Composition).
      The extensions used have been defined in VRCL for shared usage.

      Show
      The record identifiers have been moved to the Bundle Level for BFDR to be consistent with VRDR and FHIR practice (ID requried on Bundle, optional on Composition). The extensions used have been defined in VRCL for shared usage.
    • Saul kravitz / Erin Holt : 25-0-2
    • Correction
    • Non-substantive

      Each report has a record number: YYYYJJNNNNNNN
      where NNNNNN is a certificate number, JJ is the jurisdiction and YYYY is the year.
      IN addition there are two local file numbers.

      In BFDR these are maintained at the composition level as identifiers.
      In VRDR these are maintained at the bundle level as strings.

      Change BFDR to align with the VRDR model, since the identifiers rightfully belong at the bundle level.

            Unassigned Unassigned
            saul_kravitz Saul Kravitz
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: