Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

FHIR Batch Delete Based on a List of Resource IDs in Google Cloud Healthcare API

Open
  • Is something wrong?
#12,012 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@nicain is already working on this.

Since Jul 8, 2024.

Assessment

This issue has not been assessed yet.

Description

priority: p3 samples triage me type: feature request

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

The issue you're having must be related to a file in this repository. We are unable to provide assistance for issues unrelated to samples in this repository.

Please include as much information as possible:

Is your feature request related to a problem? Please describe.

I'm working on a project using the Healthcare API FHIR Storage and I'm frustrated by the difficulty of deleting all resources for a customer. The current samples include a delete_resource() function, but due to data integrity constraints in FHIR Storage, I cannot directly delete a resource if it is referenced by another resource.

Describe the solution you'd like.

I created a function called batch_delete() that receives a list of resource IDs to be deleted in a single transactional call to the Healthcare API. This function will delete all specified resources at once, ensuring transactional integrity in the FHIR Storage.

Describe alternatives you've considered.

I have tried using the delete_resource() function from this sample, but I encountered issues due to integrity constraints.

Additional context.

My idea is to contribute to this repository by creating the batch_delete() function. Additionally, I could develop a batch_deletion_by_patient_id() function, which would be highly beneficial.

Thanks!

Dominant language
Jupyter Notebook
Stars
8.1k
Forks
6.7k
Avg merge
4d 4h
Merged PRs (30d)
8

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleCloudPlatform/python-docs-samples

All issues in GoogleCloudPlatform/python-docs-samples

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.