Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#12,012 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@nicain já está trabalhando nisso.

Desde 8/7/2024.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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!

Linguagem predominante
Jupyter Notebook
Estrelas
8.1k
Forks
6.7k
Merge médio
4d 4h
PRs com merge (30d)
8

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de GoogleCloudPlatform/python-docs-samples

Todas as issues de GoogleCloudPlatform/python-docs-samples

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.