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

Ambiguity in Bundle profile

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Electronic Case Reporting (FHIR)
    • 1.1.0
    • Public Health
    • US Public Health Specification Bundle [deprecated]
    • Hide

      This is related to FHIR-30471, which suggests using an asset-collection Library, rather than a Bundle to describe the actual specification. The challenge with using a Bundle of course is that multiple bundles may be necessary to communicate the entire contents of an ERSD specification, and the contents of each bundle will vary based on the size of the specification, making it impossible to correctly describe the actual contents of the specification.

      The disposition for FHIR-30471 is as follows:
      "Define a profile of Library as an asset-collection for this purpose. Bundle is a container resource and communication of an entire eRSD specification will in general require multiple bundles, making it impossible to correctly state the constraints of the eRSD specification on the bundle. Instead, define a Library profile with asset-collection type for this purpose."

      Show
      This is related to FHIR-30471 , which suggests using an asset-collection Library, rather than a Bundle to describe the actual specification. The challenge with using a Bundle of course is that multiple bundles may be necessary to communicate the entire contents of an ERSD specification, and the contents of each bundle will vary based on the size of the specification, making it impossible to correctly describe the actual contents of the specification. The disposition for FHIR-30471 is as follows: "Define a profile of Library as an asset-collection for this purpose. Bundle is a container resource and communication of an entire eRSD specification will in general require multiple bundles, making it impossible to correctly state the constraints of the eRSD specification on the bundle. Instead, define a Library profile with asset-collection type for this purpose."
    • Sarah Gaunt / Craig Newman : 26 - 3 - 0
    • Correction
    • Compatible, substantive

    Description

      What is mean when there are required slices on an element that has cardinality of 0..*? Bundle.entry isn't required but has required slices. Does that mean that any Bundle that contains an entry has to contain all three defined slices (at a minimum)? Part of the confusion may be in the Definition of the profile. It's not clear what the scope is. I'm assuming that this profile would be used to create an eRDS bundle (as opposed to a reporting payload bundle) but it's not explicitly clear that this is the case. A similar clarification on the Supplemental Bundle profile would be appreciated.

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            craig.newman Craig Newman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: