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

Remove Bundle Identifiers

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Medicolegal Death Investigation (MDI) (FHIR)
    • 1.0.0 [deprecated]
    • Public Health
    • Bundle - Document MDI to EDRS [deprecated]
      Bundle - Message Toxicology to MDI
    • Hide

      Bundle - Document MDI to EDRS is defined as type: document.

      While the base Bundle resource structure allows 0..1 identifier, the Constraints list:

      + Rule: A document must have an identifier with a system and a value

      + Rule: A document must have a date

      + Rule: A document must have a Composition as the first resource

       

      Bundle - Message Toxicology to MDI is defined as type: message

      The base Bundle resource Constraints list only:

      + Rule: A message must have a MessageHeader as the first resource

       __ 

      Therefore, we will make the Bundle.identifier for ** Bundle - Message Toxicology to MDI optional but leave Bundle - Document MDI to EDRS as is.

      Show
      Bundle - Document MDI to EDRS is defined as type: document. While the base Bundle resource structure allows 0..1 identifier, the Constraints list: + Rule: A document must have an identifier with a system and a value + Rule: A document must have a date + Rule: A document must have a Composition as the first resource   Bundle - Message Toxicology to MDI is defined as type: message The base Bundle resource Constraints list only: + Rule: A message must have a MessageHeader as the first resource  __  Therefore, we will make the Bundle.identifier for ** Bundle - Message Toxicology to MDI optional but leave Bundle - Document MDI to EDRS as is.
    • Diana Wright / Craig Newman : 27-0-0
    • Correction
    • Non-substantive

    Description

      In the exchange bundles (MDI-to-EDRS, Toxicology-to-MDI), the profiles require an identifier. The guide has already defined identifiers in the compositions/diagnostic reports of these bundles, with care being given to assigning a type of identifier to help determine the source of the identifier.

      However, the bundle itself we cannot expect will be persisted or be maintained after exchange. The identifier for the bundle won't have any purpose beyond identifying the exchanged bundle. So it might be useful for comparing different requests. However, the logical id of the Bundle resource can also be used for this capacity. In-leiu of a strong use case for these Bundle identifiers, I propose we remove the Bundle Identifier requirements from the guide.

      Attachments

        Activity

          People

            Unassigned Unassigned
            MichaelRiley Michael Riley
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: