The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
en/CapabilityStatement-bulk-data.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' The expected capabilities of a Data Provider actor (e.g., EHR systems, data warehouses, and other clinical and administrative systems that aim to interoperate by sharing large FHIR datasets) which is responsible for providing responses to requests submitted by a Data Consumer actor. Systems implementing this capability statement SHOULD meet the requirements set by the Bulk Data Access Implementation Guide. A Data Consumer MAY choose from this list to access necessary data based on use cases and other contextual requirements. 'CONFORMANCE_STATEMENT_WORD
en/OperationDefinition-export.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' FHIR Operation through which an authenticated and authorized Data Consumer may request bulk FHIR data from a Data Provider, whether or not the data is associated with a patient. This supports use cases like backing up a Data Provider's FHIR server, or exporting terminology data by restricting the resources returned using the _type parameter. The Data Provider's FHIR Resource Server SHALL support invocation of this operation using the FHIR Asynchronous Bulk Interaction Pattern 'CONFORMANCE_STATEMENT_WORD
en/OperationDefinition-group-export.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' FHIR Operation through which an authenticated and authorized Data Consumer requests a detailed set of FHIR resources of diverse resource types pertaining to all members of the specified Group from a Data Provider. The Data Provider's FHIR Resource Server SHALL support invocation of this operation using the FHIR Asynchronous Bulk Interaction Pattern 'CONFORMANCE_STATEMENT_WORD
en/OperationDefinition-patient-export.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' FHIR Operation through which an authenticated and authorized Data Consumer requests a detailed set of FHIR resources of diverse resource types pertaining to all patients from a Data Provider. The Data Provider's FHIR Resource Server SHALL support invocation of this operation using the FHIR Asynchronous Bulk Interaction Pattern 'CONFORMANCE_STATEMENT_WORD
en/async.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Servers SHALL support the HTTP methods, URLs, headers, and other parameters that normally apply to the interaction being invoked. Servers SHALL also support the Prefer header described below, and SHOULD support the Accept header and _outputFormat parameter described below.'CONFORMANCE_STATEMENT_WORD
en/authorization.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Implementations of Bulk Export, Bulk Submit, and Bulk Submit Status SHOULD implement OAuth 2.0 access management in accordance with the SMART Backend Services Authorization Profile.'CONFORMANCE_STATEMENT_WORD
en/export.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'All exchanges described herein between a Data Consumer and a Data Provider SHALL be secured using Transport Layer Security (TLS) Protocol Version 1.2 (RFC5246) or a more recent version of TLS. Use of mutual TLS is OPTIONAL.'CONFORMANCE_STATEMENT_WORD
en/group.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Servers supporting the Bulk Data Access IG MAY support the Bulk Cohort API, which consists of an asynchronous Group creation REST interaction and a profile on the Group resource. The intent is to support the creation of characteristic-based cohorts using coarse-grained filters to efficiently export data on sets of patients from a source system. Post export, the client can use more complex filter criteria to support use cases such as measure calculation or other analytics. Groups complying with the Bulk Cohort profile SHALL contain a member-filter modifier extension to define the members included in the group. Servers MAY concurrently support other group profiles that contain lists of members or use other methods to define group inclusion.'CONFORMANCE_STATEMENT_WORD
en/index.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '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.'CONFORMANCE_STATEMENT_WORD
en/publish.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'All exchanges described herein between a Data Consumer and a Data Provider SHOULD be secured using Transport Layer Security (TLS) Protocol Version 1.2 (RFC5246) or a more recent version of TLS. Use of mutual TLS is OPTIONAL. With each of the requests described herein, implementers MAY implement OAuth 2.0 access management in accordance with the SMART Backend Services Authorization Profile.'CONFORMANCE_STATEMENT_WORD
en/submit.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'All exchanges described herein between a Data Consumer and a Data Provider SHALL be secured using Transport Layer Security (TLS) Protocol Version 1.2 (RFC5246) or a more recent version of TLS. Use of mutual TLS is OPTIONAL.'CONFORMANCE_STATEMENT_WORD
01. An inline example is provided in the extension description
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/bulkdata/StructureDefinition/operation-not-supported'): The Implementation Guide contains no examples for this extension (1 uses)
02. This new feature will be added in future versions of this IG
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause (0 uses)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause (0 uses)
03. This extension is defined in the Expression type, not in this IG
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
04. Group profile - this code system is used by the Group resource
Reference to draft CodeSystem http://hl7.org/fhir/group-type|4.0.1 (4 uses)
05. Created UTG tracker to create code system in UTG: UP-759 - "Create an Include Associated Data Code System" based on discussion with TMSG (11/13/2025 minutes: https://confluence.hl7.org/spaces/TSMG/pages/403868663/2025-11-13+TSMG+Agenda+and+Minutes). To preserve the expansion and links in the ValueSet definition, this version will use the current code system defined in this IG and will update to the THO code system URL when it is published. Since the current operation parameter that uses these codes is of type `code` and documented as experimental, this is not considered a breaking change and does not need community input. An STU note was added to alert implementers that that the code system will be migrating to THO.
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
hl7.fhir.uv.bulkdata
hl7.fhir.uv.tools.r4