FHIR Batch Delete Based on a List of Resource IDs in Google Cloud Healthcare API
Maintainer antworten meist innerhalb von 5 Tagen
@nicain arbeitet bereits daran.
Seit 08.7.2024.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
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!
- Vorherrschende Sprache
- Jupyter Notebook
- Sterne
- 8.1k
- Forks
- 6.7k
- Ø Merge
- 4 T. 12 Std.
- Gemergte PRs (30 T.)
- 9
Entwicklungsumgebung
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus GoogleCloudPlatform/python-docs-samples
-
samples
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
GoogleCloudPlatform/python-docs-samples#14609 ·
Maintainer antworten meist innerhalb von 5 Tagen
-
samples
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 92/100
GoogleCloudPlatform/python-docs-samples#14610 ·
Maintainer antworten meist innerhalb von 5 Tagen
-
samples
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
GoogleCloudPlatform/python-docs-samples#14611 ·
Maintainer antworten meist innerhalb von 5 Tagen
-
chore(generative_ai) Update model references for generative_ai samplesEvtl. wieder frei @XrossFox hat das vor 153 Tagen übernommen, und es ist kein Pull Request offen. Offensamples
GoogleCloudPlatform/python-docs-samples#14117 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen
-
Fix Pipeline dependency issues for geospatial-classification/serving_appEvtl. wieder frei @XrossFox hat das vor 165 Tagen übernommen, und es ist kein Pull Request offen. Offensamples
GoogleCloudPlatform/python-docs-samples#14091 · 1 zugewiesene Person ·
Maintainer antworten meist innerhalb von 5 Tagen