FHIR Batch Delete Based on a List of Resource IDs in Google Cloud Healthcare API
I maintainer di solito rispondono entro 5 giorni
@nicain ci sta già lavorando.
Dal 8/7/2024.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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!
- Lingua principale
- Jupyter Notebook
- Stelle
- 8.1k
- Fork
- 6.7k
- Merge medio
- 4g 12h
- PR unite (30g)
- 9
Preparare l'ambiente
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di GoogleCloudPlatform/python-docs-samples
-
samples
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
GoogleCloudPlatform/python-docs-samples#14609 ·
I maintainer di solito rispondono entro 5 giorni
-
samples
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
GoogleCloudPlatform/python-docs-samples#14610 ·
I maintainer di solito rispondono entro 5 giorni
-
samples
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
GoogleCloudPlatform/python-docs-samples#14611 ·
I maintainer di solito rispondono entro 5 giorni
-
chore(generative_ai) Update model references for generative_ai samplesForse di nuovo libera @XrossFox l’ha presa 154 giorni fa e non c’è nessuna pull request aperta. Apertasamples
GoogleCloudPlatform/python-docs-samples#14117 · 1 assegnatario ·
I maintainer di solito rispondono entro 5 giorni
-
Fix Pipeline dependency issues for geospatial-classification/serving_appForse di nuovo libera @XrossFox l’ha presa 166 giorni fa e non c’è nessuna pull request aperta. Apertasamples
GoogleCloudPlatform/python-docs-samples#14091 · 1 assegnatario ·
I maintainer di solito rispondono entro 5 giorni