The updated publication of the original PDF-published version of the informational white paper.
changes
change.html
first
true
category
Public Health
title
Bulk Retrieval of Public Health Data
introduction
This document is designed to assist public health professionals in understanding the capabilities of Bulk FHIR and to promote a unified method across the sector. The Bulk FHIR data access method facilitates the sharing of data on populations of individuals and is a Priority Area for the Helios FHIR Accelerator for Public Health. This approach allows users of Electronic Health Records (EHR) systems and other electronic platforms to utilize the carefully curated data managed by public health programs. By implementing FHIR Bulk data, authorized users can efficiently retrieve data for defined groups through a standardized and reusable method. This process enables public health systems to generate and transmit essential information quickly while reducing the time and effort needed to respond to data requests in proprietary and custom formats.
Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/us/ph-bulk-data (Problem #1 with package-list.json at http://hl7.org/fhir/us/ph-bulk-data: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
01: The "SHALL" is part of a quoted passage from the Bulk Data Access FHIR IG which explains the various parameters. The Helios document does not add any additional conformance requirements.
INFORMATION: en/technical.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: '_type Server Usage: Optional Client Usage: Optional Description: A string of comma-delimited FHIR resource types. The response SHALL be filtered to only include resources of the specified resource types(s). ' (1 uses)
02: The differences are that the main Jira Spec Artifact contains a version 1.0.0 which is the original PDF publication version. This is not in the IG publisher jira-new.xml (see https://chat.fhir.org/#narrow/channel/184932-JIRA.2FConfluence/topic/How.20to.20handle.20a.20specification.20key.20change/with/576132153)
WARNING: 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) (1 uses)
04: Related to ExampleScenario and the IG publisher (Ok to suppress for ballot per FMG QA review on 3/17/2026) (see https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/ExampleScenario.20errors/with/574541506)
%The link 'node1' for "details" cannot be resolved% (1 uses)
%The link 'node10' for "Cohort Create or Update" cannot be resolved% (1 uses)
%The link 'node12' for "Bulk Data Export" cannot be resolved% (1 uses)
%The link 'node12' for "response" cannot be resolved% (1 uses)
%The link 'node2' for "details" cannot be resolved% (1 uses)
%The link 'node3' for "details" cannot be resolved% (1 uses)
%The link 'node4' for "details" cannot be resolved% (1 uses)
%The link 'node6' for "Immunization Administration Event Submission" cannot be resolved% (1 uses)
%The link 'node8' for "Patient Identification Query" cannot be resolved% (1 uses)
%The link 'node8' for "response" cannot be resolved% (1 uses)