Sent Report

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.