Sent Report: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
ENagy (talk | contribs)
m Text replacement - "CCMDB.mdb" to "CCMDB.accdb"
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The sent report is an MS Access report generated by the [[CCMDB.mdb]] at the end of [[Sending Patients|sending patients]]. '''Don't confuse it with the [[PDA Status.csv]] which is generated at the same time and where you need to fill in a reason why a discharged patient was not sent. '''
'''Legacy only: The Sent Report will no longer be used as of 2014-Jul-31'''
 
 
----
 
 
Hi everyone - Changes- We no longer require this report to be printed out at sites, filed in offices, with batch numbers written on them or sent in to HSC site with the ICU TISS forms. We will be eliminating this extra burden of data collection activity. Some of the staff have been continuing this activity as trained to do in the beginning, but we will be changing it.  As you know, when a batch is sent the actual CSV sent file is opened up and a collector can actually see and verify on the spot visually who was sent in the batch.  Once this is done visually, the printout of names as evidence of who was in the batch is not required.  Pagasa provides collectors with necessary information to follow up on any files. This was a list that was useful in the past when we first started electronic processing but with the many improvement to electronic processing, the main office can track what is sent and not sent in in new data repository therefore the collectors no longer need a printed list, or save a list of names and record a batch number.  Tina is working on this, once she has this done, this sent list will be eliminated summer of 2014. -[[User:TOstryzniuk|Trish Ostryzniuk]] 19:29, 2014 July 10 (CDT)
 
The sent report is an MS Access report generated by the [[CCMDB.accdb]] at the end of [[Sending Patients|sending patients]]. '''The report does '''not''' need to be printed and filed locally or sent to the [[main office]]. '''


== Use and processing ==
== Use and processing ==
Data collectors keep this and use it to find records for patients when Pagasa wants them to look something up. I don't understand how that process works or why this report is helpful. Could someone please add this here? If I know how this is used I might be able to make it more helpful, e.g. by adding more fields. [[User:Ttenbergen|Ttenbergen]] 10:49, 24 September 2009 (CDT)  
Data collectors keep this and use it to find records for patients when Pagasa wants them to look something up. I don't understand how that process works or why this report is helpful. Could someone please add this here? If I know how this is used I might be able to make it more helpful, e.g. by adding more fields. [[User:Ttenbergen|Ttenbergen]] 10:49, 24 September 2009 (CDT)  


'''You don’t need to send a copy of the Sent Report to us.  Some of you were sending them in with your batch of green sheets. 
== Potential Change Checklist ==
 
=== data storage ===
== To print/file or not? ==
* store the following in [[CCMDB_data.mdb]]:
{{Discussion}}
** batch number
Some of the sites were using them as a list to keep batch numbers organized and also to know which ones to delete after sending.
** file name generated as
How does your site use this? Do you print it out or not? Collectors used to be required to print these out and then put your batch number on top and file it. Does your site still do this? How do you use them the send report? 
** send date
 
** (generated patient count per batch, this would not be stored)
===HSC===
** also, for each patient store patient name, id and batch
The status report is not printed out but allows us to indicate why the patient file was not sent ie:chart in medical records as patient discharged/deceased, awaiting pathology or lab results, etc. This way Pagasa and Julie know the reason for the delay. As far as the send report goes , it allows for faster retrieval of a patient's info using our hard copies kept on file (since the e-file is deleted once sent)as opposed to pulling a chart from Medical Records.--[[User:CMarks|CMarks]] 11:59, 24 August 2010 (CDT)


===OAKS===
=== interface changes ===
Does not have a printer connected to the laptop. The status report was never printed when there was a printer-for the same reasons cited by Con. As for the sent report; when there was a printer a copy of the sent report was printed (one sent to Pagasa with Tiss sheets and one for records here). I now write out the list of sent records for each batch to keep on record.  OAKS does not collect on paper; so the chart would have to be accessed from medical records to obtain any information.--[[User:Mlaporte|Mlaporte]] 09:07, 25 August 2010 (CDT)
* add new button to front page to open "sent batches"
* add new sortable form that lists all patients with their info as per above
** can we minimize this? only list initials? possibly only the id? What is actually needed to find patients Pagasa sent? Since I '''still''' don't understand how this helps I don't know what is needed. I still think that, for the most part, Pagasa should be able to provide enough info with any request that none of this would need to be stored locally. Ttenbergen 16:01, 2012 November 19 (EST)


===GRA_Med===
* Can you think of other data that would be helpful on this form?
Hi Trish,
*1. [[PDA Status.csv]]- I have never printed this report. I do fill this out as required when there is a patient with a discharge date but I don't send the profile for whatever the reason on the report.
*2. Sent Report- This report I take a copy of and file this in the binder per your instructions. I also use this report in finding data/ who sent the report and where I might find the information that you, Julie or Pagasa may need. I never send this report to HSc. Tara, Jan 14.10


===Vic Med ===
* '''pre-fill the batch number''' in sending with the likely next one, but leave it editable; make it fail gracefully by not pre-populating a number if most recent "number" wasn't a number, e.g. in case of re-sends.  
*Hi Trish
*[[PDA Status.csv]]: I do complete this report by adding in the reason the chart is not complete if there is a discharge date. I do not print this report to save or send anywhere.
*Send Report: This is the report I print a copy for the binder you have given us and it is filed in the drawer. I use this report to go through my log and make sure I have completed that. And I also can quickly refer to this when Pagasa calls with a question to reflect the batch. Hope this is the information you require. Wendy Gobert R.N. Jan 14.10


=== CON ===
* since this is stored in ccmdb_data it will be available in backups for main office as needed
See [[#OAKS]]


=== STB ===
=== other fields? ===
what do they do? [[User:Ttenbergen|Ttenbergen]] 10:35, 2012 September 6 (CDT) {{discussion}}
* Debbie at StB also puts on her report "ward, medicine, SBGH, my initials, and the date I sent." Not sure how this would be used, but it would be easy enough to include. Personally I don't think it adds anything and would only fill space. How would including this help anyone? Ttenbergen 16:01, 2012 November 19 (EST)  
*I have never printed the PDA Status.csv report.I print a copy of the sent report for my binder for exactly all the reasons listed by the others above. I use it as a quick reference for who I have sent, and when I have sent them. I often have to check this several times a week. If you are going to add more fields, at the top where the form says "Sent Files for Batch______", I also write in my ward, medicine, SBGH, my initials, and the date I sent. [[User:DPageNewton|DPageNewton]] 10:50, 2012 October 29 (EDT)  


**we no longer need to be doing this. -[[User:TOstryzniuk|Trish Ostryzniuk]] 21:29, 2012 November 19 (EST)


  I do not print out PDA Status.csv report, but I enter reason(s) for not sending file in batch in  this report. I print a copy of the Sent Report as it provides me with a quick reference as to which serial#/file was sent in which batch.[[User:ENagy|ENagy]] 15:20, 2012 October 30 (EDT)
=== clean-up ===
'''Legacy info only below here!
Notes field used to auto-generate content for this, make sure all that is cleaned up when reprogramming. Ttenbergen 16:08, 2012 November 19 (EST)


== Legacy Info ==
== Legacy Info ==
Line 42: Line 44:




[[Category: Data Collection Guide]]
[[Category:Legacy forms]]

Latest revision as of 12:01, 22 September 2019

Legacy only: The Sent Report will no longer be used as of 2014-Jul-31




Hi everyone - Changes- We no longer require this report to be printed out at sites, filed in offices, with batch numbers written on them or sent in to HSC site with the ICU TISS forms. We will be eliminating this extra burden of data collection activity. Some of the staff have been continuing this activity as trained to do in the beginning, but we will be changing it. As you know, when a batch is sent the actual CSV sent file is opened up and a collector can actually see and verify on the spot visually who was sent in the batch. Once this is done visually, the printout of names as evidence of who was in the batch is not required. Pagasa provides collectors with necessary information to follow up on any files. This was a list that was useful in the past when we first started electronic processing but with the many improvement to electronic processing, the main office can track what is sent and not sent in in new data repository therefore the collectors no longer need a printed list, or save a list of names and record a batch number. Tina is working on this, once she has this done, this sent list will be eliminated summer of 2014. -Trish Ostryzniuk 19:29, 2014 July 10 (CDT)

The sent report is an MS Access report generated by the CCMDB.accdb at the end of sending patients. The report does not need to be printed and filed locally or sent to the main office.

Use and processing

Data collectors keep this and use it to find records for patients when Pagasa wants them to look something up. I don't understand how that process works or why this report is helpful. Could someone please add this here? If I know how this is used I might be able to make it more helpful, e.g. by adding more fields. Ttenbergen 10:49, 24 September 2009 (CDT)

Potential Change Checklist

data storage

  • store the following in CCMDB_data.mdb:
    • batch number
    • file name generated as
    • send date
    • (generated patient count per batch, this would not be stored)
    • also, for each patient store patient name, id and batch

interface changes

  • add new button to front page to open "sent batches"
  • add new sortable form that lists all patients with their info as per above
    • can we minimize this? only list initials? possibly only the id? What is actually needed to find patients Pagasa sent? Since I still don't understand how this helps I don't know what is needed. I still think that, for the most part, Pagasa should be able to provide enough info with any request that none of this would need to be stored locally. Ttenbergen 16:01, 2012 November 19 (EST)
  • Can you think of other data that would be helpful on this form?
  • pre-fill the batch number in sending with the likely next one, but leave it editable; make it fail gracefully by not pre-populating a number if most recent "number" wasn't a number, e.g. in case of re-sends.
  • since this is stored in ccmdb_data it will be available in backups for main office as needed

other fields?

  • Debbie at StB also puts on her report "ward, medicine, SBGH, my initials, and the date I sent." Not sure how this would be used, but it would be easy enough to include. Personally I don't think it adds anything and would only fill space. How would including this help anyone? Ttenbergen 16:01, 2012 November 19 (EST)
    • we no longer need to be doing this. -Trish Ostryzniuk 21:29, 2012 November 19 (EST)

clean-up

Notes field used to auto-generate content for this, make sure all that is cleaned up when reprogramming. Ttenbergen 16:08, 2012 November 19 (EST)

Legacy Info

Report used to list the same patients in three columns since we went to the new program. At the time there were some concerns about patients being shown in the program as sent, but not actually being sent. I removed the duplicate data today and made the text bigger instead.