Skip to content

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

Open

Description

@baptvit

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!

Activity

  1. added
    priority: p3Desirable enhancement or fix. May not be included in next release.
    triage meI really want to be triaged.
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    on Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p3Desirable enhancement or fix. May not be included in next release.samplesIssues that are directly related to samples.triage meI really want to be triaged.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions