Skip to content
New issue

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

Increase Update Frequency for Clinical Research Database #410

Open
jonc101 opened this issue Sep 9, 2024 · 1 comment
Open

Increase Update Frequency for Clinical Research Database #410

jonc101 opened this issue Sep 9, 2024 · 1 comment
Assignees
Labels
DependencyRisk Depends on someone else, so can't assure attention MultiPart Complex issues that really require multiple sub-parts Priority - 2 Medium Prioritize over maintenance issues, but not immediately critical.

Comments

@jonc101
Copy link
Collaborator

jonc101 commented Sep 9, 2024

Message sent to Yelena on 9/9/2024

We've thus far been updating our copy of the Stanford electronic medical record data about once per year.

What would it take to be able to do this updates more frequently?

Hopefully most of the process could be automated, so it's not a manual step every time.
The Hospitalist division wants to do analysis that needs more up to date information to monitor different processes.

In theory, that could mean wanting an update every day.
In practice, an update every week or even every month could be sufficient.
Would be an engineering tradeoff guided by how easy or hard it is to implement.

Can you also investigate how to retrieve the clinical Voalte messaging data?
This is the secure messaging app that clinical staff in the hospital use to communicate with each other.
Hospitalist division again interested in using it to understand where clinical time is being spent.
I can update our IRB to include these as well, though we already include "Clinical narratives or reports" for the notes, so that may include these as well.

@jonc101 jonc101 added Priority - 2 Medium Prioritize over maintenance issues, but not immediately critical. MultiPart Complex issues that really require multiple sub-parts DependencyRisk Depends on someone else, so can't assure attention labels Sep 9, 2024
@jonc101 jonc101 self-assigned this Sep 9, 2024
@jonc101 jonc101 added this to DevOps Sep 9, 2024
@github-project-automation github-project-automation bot moved this to To Do in DevOps Sep 9, 2024
@jonc101
Copy link
Collaborator Author

jonc101 commented Dec 11, 2024

  • Establish regular update interval (process in place)
  • Access log update interval define
  • Deid note update interval timing
  • Add SmartDataElements (to reconstruct Smart BPA processes)
  • Add Level of Service Billing Code data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DependencyRisk Depends on someone else, so can't assure attention MultiPart Complex issues that really require multiple sub-parts Priority - 2 Medium Prioritize over maintenance issues, but not immediately critical.
Projects
Status: To Do
Development

No branches or pull requests

1 participant