201801 Bulk Data
Bulk Data Access
Submitting WG/Project/Implementer Group
This track is created at the request of the ONC. ONC provided this justification:
- Ecosystem outcome expected to enable many specific use case/business needs: Providers and organizations accountable for managing the health of populations can efficiently access to large volumes of informationon a specified group of individuals without having to access one record at a time. This population-level access would enable these stakeholders to: assess the value of the care provided, conduct population analyses, identify at-risk populations, and track progress on quality improvement.
- Technical Expectations: There would be a standardized method built into the FHIR standard to support access to and transfer of a large amount of data on a specified group of patients and that such method could be reused for any number of specific business purposes.
- Policy Expectations: All existing legal requirements for accessing identifiable patient information via other bulk methods (e.g., ETL) used today would continue to apply (e.g., through HIPAA BAAs/contracts, Data Use Agreements, etc).
Proposed Track Lead
Dan Gottleib with support from Grahame Grieve (Connectathon_Track_Lead_Responsibilities)
- Grahame Grieve
- CARIN health alliance
Data Provider: provides data in the manner specified by the bulk data API Data Consumer: consumes data in the manner specified by the bulk data API and displays/processes the data
The bulk data track is divided into 3 scenarios:
- asynchronous access
- nd-json support
- smart back-end services
Participants are encouraged to support either of the following initiation points:
- GET [base]/Patient/[id]/$everything
- GET [base]/Patient/$everything
However for the purposes of this connectathon track, data providers can nominate any other URL to initiate the process, as long as it returns a FHIR Bundle
Scenario Step 1: Asynchronous Access
- Precondition: Use the nominated URL for the
- Success Criteria:
- Bonus point: