We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create 3 new API endpoints to assign with managing orphaned (unlinked) data.
DELETE /person/<person-reference-id> This should delete an EMPTY person cluster, if the person cluster has members this should result in an error.
DELETE /person/<person-reference-id>
GET /person/orphaned A paginated list of all the persons with no members.
GET /person/orphaned
GET /patient/orphaned A paginated list of all the patients not yet assigned to a person cluster.
GET /patient/orphaned
GET /person/orphaned could be an expensive query to run, give this query a lot of consideration so we know it will scale with large databases.
#155
This will complete use cases 12 and 13 in #155.
The text was updated successfully, but these errors were encountered:
m-goggins
No branches or pull requests
Summary
Create 3 new API endpoints to assign with managing orphaned (unlinked) data.
Details / Tasks
DELETE /person/<person-reference-id>
This should delete an EMPTY person cluster, if the person cluster has members this should result in an error.
GET /person/orphaned
A paginated list of all the persons with no members.
GET /patient/orphaned
A paginated list of all the patients not yet assigned to a person cluster.
Background / Context
GET /person/orphaned
could be an expensive query to run, give this query a lot of consideration so we know it will scale with large databases.Related Issues/PRs
#155
Notes / Comments
This will complete use cases 12 and 13 in #155.
The text was updated successfully, but these errors were encountered: