Skip to content

Commit

Permalink
Changes by HS, sent to DRM.
Browse files Browse the repository at this point in the history
  • Loading branch information
zimolzak committed Oct 11, 2021
1 parent 1ebbfa7 commit ed190c6
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 14 deletions.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,4 @@ instruct-trigger-manual.txt
*.png
advanced/*.docx
advanced/discovery-appendices.md
advanced/discovery-manual-with-appendices.md
29 changes: 15 additions & 14 deletions advanced/discovery.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,14 @@
% Cancer Test Result e-Trigger Manual

Sahar Memon, Andrew Zimolzak, Li Wei
**Guidance complied by:** Sahar Memon, Andrew Zimolzak, Li Wei, Daniel
Murphy, Hardeep Singh.

VA Houston / Baylor College of Medicine
**Affiliation:** Michael E. DeBakey Veterans Affairs Medical Center,
and Baylor College of Medicine. Houston, TX, USA.

October, 2021
**For questions:** [[email protected]](mailto:[email protected]) and [[email protected]](mailto:[email protected])

**Date:** October, 2021



Expand Down Expand Up @@ -51,7 +55,9 @@ that you cite:

# How are the e-triggers designed?

An e-trigger answers the question, "How do you find (in the database)
The lung and colorectal e-triggers are examples of one type of
e-trigger, which we call a *close the loop e-trigger.* These two
e-triggers answer the question, "How do you find (in the database)
patients who had a test that shows a possibility of cancer, but who
have **not** had timely follow-up?"

Expand All @@ -68,9 +74,9 @@ the e-triggers in local SQL.
## Downloading the SQL code

1. The most recent version of the code can be downloaded from
github.com/zimolzak/instruct-project-etrigger-sql where you can
also find additional procedures for setting dates, and guidance
about which tables to export for final reporting.
[github.com/zimolzak/instruct-project-etrigger-sql](https://github.com/zimolzak/instruct-project-etrigger-sql)
where you can also find additional procedures for setting dates,
and guidance about which tables to export for final reporting.

2. Before downloading, jot down or copy/paste the text in the bar near
the top of GitHub, especially the **seven random-looking letters
Expand All @@ -85,8 +91,6 @@ the e-triggers in local SQL.
5. Use your browser menu to save file to disk (such as "File / Save
Page As...").

Email [email protected] with any questions.




Expand Down Expand Up @@ -172,11 +176,8 @@ continues to capture usage of both the historical and new codes).
# Further reading (relevant files/attachments)

- Reducing Missed Test Results Change Package
- e-Trigger Standard Operating Procedure (the figure "SOP for
DISCovery.pptx" and the explanatory legend "DISCOVERY SOP
text....docx")
- `Lung.sql` code file
- `Fobt.sql` code file
- `Lung.sql` code file (see GitHub)
- `Fobt.sql` code file (see GitHub)


---
Expand Down

0 comments on commit ed190c6

Please sign in to comment.