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

Issues with Packaging and Bundle profiles

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive
    • Specification:
      US Quality Measures (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Clinical Quality Information
    • Related Page(s):
      Profiles
    • Grouping:
    • Resolution Description:
      Hide

      Remove the bundle-based profiles (CQFMLibraryBundle, CQFMMeasureBundle, and CQFMTestCaseBundle), clarify guidance on packaging conformance requirements may span multiple bundles in a given delivery, and indicate that bundles should be "transaction" bundles when they are used for distribution, indicating the bundle should be processed as a unit.
      Note that if an artifact package is large enough to require segmentation in multiple bundles, use of transaction bundles may not be feasible.

      Show
      Remove the bundle-based profiles (CQFMLibraryBundle, CQFMMeasureBundle, and CQFMTestCaseBundle), clarify guidance on packaging conformance requirements may span multiple bundles in a given delivery, and indicate that bundles should be "transaction" bundles when they are used for distribution, indicating the bundle should be processed as a unit. Note that if an artifact package is large enough to require segmentation in multiple bundles, use of transaction bundles may not be feasible.
    • Resolution Vote:
      Abdullah Rafiqi/Stan Rankin:22-0-1
    • Change Category:
      Correction
    • Change Impact:
      Non-compatible

      Description

      Current packaging guidance uses Bundle profiles to establish expectations for delivery packages for artifacts. These profiles specify a bundle type of "collection". However, when using collection, fullUrl is required, and there is no guidance about what the value of that element should be, or how it would be expected to be used by consuming systems.

      In addition, the use of "transaction" bundles is more aligned with the target use case of a "deployment" package.

      Consider alternate approaches to expressing the constraints for the package, and provide better guidance about use of "transaction" as opposed to "collection" bundles for the purposes of distribution, especially how the request and/or fullUrl elements of the bundle are expected to be used by both by authoring systems from a packaging perspective, and implementing systems from a consumption/ingestion perspective.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bryn.rhodes Bryn Rhodes
              Reporter:
              bryn.rhodes Bryn Rhodes
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: