"exclude" button: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
Line 2: | Line 2: | ||
== Workings of the "exclude" button == | == Workings of the "exclude" button == | ||
=== In [[Cognos Report Integrator]] == | |||
When clicked in [[Cognos Report Integrator]], the {{PAGENAME}} will exclude the record from future lists if the '''AsgnUnitStartDtm_current''' / '''[[Arrive DtTm]]''' resp [[EPR Admit DtTm]] match the excluded one. | |||
=== In [[EPR Reports Integrator]] === | |||
When clicked in [[EPR Reports Integrator]], the {{PAGENAME}} will exclude the record from future lists if the '''Service Start Dtm''' / '''[[Accept DtTm]]''' resp [[EPR Admit DtTm]] match the excluded one. | |||
Pulling a discussion here from an email | Pulling a discussion here from an email | ||
{{Discuss | | {{Discuss | | ||
* I am reluctant to tus the exclude button because in the past with the integrator, when I used the exclude button and the patient was readmitted it would not show up. Will this be the same for cognos? The exclude button works based on excluding records with that chart and that service start / accept date and time. This is still based on what it was in EPR Integrator, and of course, it hides future moves of that patient. | * I am reluctant to tus the exclude button because in the past with the integrator, when I used the exclude button and the patient was readmitted it would not show up. Will this be the same for cognos? The exclude button works based on excluding records with that chart and that service start / accept date and time. This is still based on what it was in EPR Integrator, and of course, it hides future moves of that patient. | ||
** | ** '''No, this should not be a problem in Cognos'''. EPR Integrator excluded by [[Arrive_DtTm]]/''Service Start Dtm'' resp [[EPR Admit DtTm]]. Excluding based on that meant that, if a patient changes units later on but remains on the same service, those moves would be hidden as well. That's why it changed to Unit Start Dtm in Cognos. The EPR Reports use inconsistent values for this so I don't think we can change its behaviour to be same as Cognos, this was one of the main reasons we went to Cognos data: it doesn't consist of three uncomparable lists. | ||
}} | }} | ||
Revision as of 16:47, 2020 June 16
The "exclude" button hides records that have been vetted by a collector as something we don't need to collect in EPR Reports Integrator and Cognos Report Integrator .
Workings of the "exclude" button
= In Cognos Report Integrator
When clicked in Cognos Report Integrator, the "exclude" button will exclude the record from future lists if the AsgnUnitStartDtm_current / Arrive DtTm resp EPR Admit DtTm match the excluded one.
In EPR Reports Integrator
When clicked in EPR Reports Integrator, the "exclude" button will exclude the record from future lists if the Service Start Dtm / Accept DtTm resp EPR Admit DtTm match the excluded one.
Pulling a discussion here from an email
|
When might a record be marked as excluded?
- patient at a location that we include where only some of the patients are ours
- patients on one of our locations who belong to a service we don't collect
- beds borrowed by another service on one of our wards
Mistakes
If a record has been mistakenly excluded, use the "View excludeds" button in EPR Reports Integrator and Cognos Admitter to bring it back.