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

Bulk Data - Issues within Exchange Capability Statement

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • National Directory of Healthcare Providers and Services (NDH) (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • STU
    • Exchange Implementation Guidance
    • 5.4
    • Hide

      The response for item 1.

      In the Bulk Data Access Implementation Guide (IG), it is stated, "To declare conformance with this IG, a server should include the following URL in its CapabilityStatement.instantiates: http://hl7.org/fhir/uv/bulkdata/CapabilityStatement/bulk-data - http://hl7.org/fhir/uv/bulkdata/#conformance." The Bulk Data Access IG's CapabilityStatement/bulk-data outlines three operations: group-export, patient-export, and system-export. However, the NDH IG only utilizes the system-export operation; the other two operations in the Bulk Data Access IG are irrelevant to the NDH IG. Consequently, the NDH IG should not include the Bulk Data Access IG conformance in its exchange capability statement. Instead, the NDH IG will define its conformance through narrative outside the capability statement.

      The response for item 2.

      In the NDH IG, dependency checks list hl7/fhir/uv/bulkdata version 2.0.0.

      The response for item 3.

      The NDH IG's CapabilityStatement.rest.resource.operation will incorporate the export function.

      The response for item 4 and 5 

      The NDH IG will not create a new export operation data structure definition in addition to the existing export operation of the Bulk Data Access IG. Instead, it will utilize the Bulk Data Access IG's export operation data structure definition as is. The NDH IG will establish its own conformance criteria within the Guidance conformance section (parameters, responses ...).

      Show
      The response for item 1. In the Bulk Data Access Implementation Guide (IG), it is stated, "To declare conformance with this IG, a server should include the following URL in its CapabilityStatement.instantiates:  http://hl7.org/fhir/uv/bulkdata/CapabilityStatement/bulk-data  -  http://hl7.org/fhir/uv/bulkdata/#conformance ." The Bulk Data Access IG's CapabilityStatement/bulk-data outlines three operations: group-export, patient-export, and system-export. However, the NDH IG only utilizes the system-export operation; the other two operations in the Bulk Data Access IG are irrelevant to the NDH IG. Consequently, the NDH IG should not include the Bulk Data Access IG conformance in its exchange capability statement. Instead, the NDH IG will define its conformance through narrative outside the capability statement. The response for item 2. In the NDH IG, dependency checks list hl7/fhir/uv/bulkdata version 2.0.0. The response for item 3 . The NDH IG's CapabilityStatement.rest.resource.operation will incorporate the export function. The response for item 4 and 5   The NDH IG will not create a new export operation data structure definition in addition to the existing export operation of the Bulk Data Access IG. Instead, it will utilize the Bulk Data Access IG's export operation data structure definition as is. The NDH IG will establish its own conformance criteria within the Guidance conformance section (parameters, responses ...).
    • Bob Dieterle / Ming Dunajick: 10-0-0
    • Enhancement
    • Non-compatible

    Description

      The Capability Statement for Exchange does not include requirements outlined in the Bulk Data Access IG. The following issues were identified:

      1. To declare conformance with this IG, a server should include the following URL in its CapabilityStatement.instantiates: http://hl7.org/fhir/uv/bulkdata/CapabilityStatement/bulk-data - http://hl7.org/fhir/uv/bulkdata/#conformance
      2. The version of the bulk data IG should be included.
      3. The operation $export is not included in the Capability Statement, but is used in the explanations/guidance - http://hl7.org/fhir/uv/bulkdata/OperationDefinition-export.html / https://hl7.org/fhir/us/ndh/2023Sep/exchange-ig.html#ndh-exchange-bulk-data-conformance-requirements
      4. When/if $export is added, the parameters and the obligation for the parameter(s) should be listed instead of only being listed under Guidance. https://hl7.org/fhir/us/ndh/2023Sep/exchange-ig.html#ndh-exchange-bulk-data-conformance-requirements
      5. The Capability Statement lists xml as a supported format for resources, but the IG indicates that only nd-json is available for Bulk Data $export. Will that be added to the capability statement? https://hl7.org/fhir/us/ndh/2023Sep/exchange-ig.html#format-of-the-bulk-data-extract
        #will includeAssociatedData be required or part of the requirements or will it be an implementation decision that is not part of the requirements?

      Attachments

        Activity

          People

            Unassigned Unassigned
            ricklisseveld Rick Lisseveld
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: