Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#12,012 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

@nicain がすでに取り組んでいます。

2024年7月8日 から。

評価

この issue はまだ評価されていません。

説明

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!

主要言語
Jupyter Notebook
スター
8.1k
フォーク
6.7k
平均マージ
4日 4時間
マージ済み PR(30日)
8

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

GoogleCloudPlatform/python-docs-samples のほかの issue

GoogleCloudPlatform/python-docs-samples の issue をすべて見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。