Sending Patients: Difference between revisions

(3 intermediate revisions by 2 users not shown)

Line 9:

*'''Don't cut it close''' - if you have come really close to the end of the send window and might not '''finish sending''' before the window closes, just don't send and let Pagasa know. If you are still sending while Pagasa [[pull]]s the data we get discrepancies that need to be resolved. It's easier if we just know you didn't get to it and can organize to have you send later if needed.

*At each send, [[Minimal Data Set]] applies.

{{Discuss| Can we again revisit the pros and cons of sending only when working on site against sending from home? There is always a need of updated data and I do not want to be emailing everyone to send when data are needed. This can be solved by sending in all days the collector works regardless onsite or from home during the assigned time slots. In addition, I think this practice of submitting data frequently will also mean lesser new data on the laptop if unfortunate incident happens on the laptop and there is a need to re-enter data again. Do we still experience problem in sending when we set up the sending time schedule by site? --[[User:JMojica|JMojica]] 16:37, 2 December 2025 (CST)}}

{{Discuss| JALT

* Can we again revisit the pros and cons of sending only when working on site against sending from home? There is always a need of updated data and I do not want to be emailing everyone to send when data are needed. This can be solved by sending in all days the collector works regardless onsite or from home during the assigned time slots. In addition, I think this practice of submitting data frequently will also mean lesser new data on the laptop if unfortunate incident happens on the laptop and there is a need to re-enter data again. Do we still experience problem in sending when we set up the sending time schedule by site? --[[User:JMojica|JMojica]] 16:37, 2 December 2025 (CST)

** Sure, let's discuss. As far as I know, the following errors related to sending: [[Error "Invalid SQL statment..." when sending]], [[Error "Unrecognized database format" when sending]], [[Error: Centralized data.mdb not found. Contact the main office and find out if it is off-line right now.]]. I might be missing others. Sending from home takes considerably longer and has led to more errors. The fact that it takes longer requires longer send windows and reduces Pagasa's time to clean the data. When errors do happen and we need to recover this also takes significant time on Pagasa's part. AFAIK failure of the data set on the collector's laptop is very rare, I can't remember the last time I helped someone recover from that.

:: There might be ways to make sending faster or more reliable. This would take a fair bit of analysis and testing.

:: One reason I have not pursued this is the prospect of re-platforming. A cloud based system would eliminate sending; it might cause new process tangles but that's a different topic. So it would be good to have an idea of the time horizon for this to decide if the work to mitigate the errors and reduce sending restrictions is worth it.

:: It might be possible to find a compromise that re-balances risk and benefit. [[User:Ttenbergen|Ttenbergen]] 01:19, 3 December 2025 (CST)

* I heard nothing from the collectors about errors in sending since we started this new schedule. If they work from home, can we allow them to send? They can send early or after 04:30 PM. [[User:PTorres|PTorres]] 14:27, 3 December 2025 (CST)

** Open to it. If things work fine now, changing process may break them again. [[User:Ttenbergen|Ttenbergen]] 11:50, 17 December 2025 (CST)

}}

== Ongoing preparation during collection ==

@@ Line 9: / Line 9: @@
 *'''Don't cut it close''' - if you have come really close to the end of the send window and might not '''finish sending''' before the window closes, just don't send and let Pagasa know. If you are still sending while Pagasa [[pull]]s the data we get discrepancies that need to be resolved. It's easier if we just know you didn't get to it and can organize to have you send later if needed.
 *At each send, [[Minimal Data Set]] applies.
-{{Discuss| Can we again revisit the pros and cons of sending only when working on site against sending from home? There is always a need of updated data and I do not want to be emailing everyone to send when data are needed.  This can be solved by sending in all days the collector works regardless  onsite or from home during the assigned time slots. In addition, I think this practice of submitting data frequently  will also mean lesser new data on the laptop if unfortunate incident happens on the laptop and there is a need to re-enter data again. Do we still experience problem in sending when we set up the sending time schedule by site?  --[[User:JMojica|JMojica]] 16:37, 2 December 2025 (CST)}}
+{{Discuss| JALT
+* Can we again revisit the pros and cons of sending only when working on site against sending from home? There is always a need of updated data and I do not want to be emailing everyone to send when data are needed.  This can be solved by sending in all days the collector works regardless  onsite or from home during the assigned time slots. In addition, I think this practice of submitting data frequently  will also mean lesser new data on the laptop if unfortunate incident happens on the laptop and there is a need to re-enter data again. Do we still experience problem in sending when we set up the sending time schedule by site?  --[[User:JMojica|JMojica]] 16:37, 2 December 2025 (CST)
+** Sure, let's discuss. As far as I know, the following errors related to sending: [[Error "Invalid SQL statment..." when sending]], [[Error "Unrecognized database format" when sending]], [[Error: Centralized data.mdb not found. Contact the main office and find out if it is off-line right now.]]. I might be missing others. Sending from home takes considerably longer and has led to more errors. The fact that it takes longer requires longer send windows and reduces Pagasa's time to clean the data. When errors do happen and we need to recover this also takes significant time on Pagasa's part. AFAIK failure of the data set on the collector's laptop is very rare, I can't remember the last time I helped someone recover from that.
+:: There might be ways to make sending faster or more reliable. This would take a fair bit of analysis and testing.
+:: One reason I have not pursued this is the prospect of re-platforming. A cloud based system would eliminate sending; it might cause new process tangles but that's a different topic. So it would be good to have an idea of the time horizon for this to decide if the work to mitigate the errors and reduce sending restrictions is worth it.
+:: It might be possible to find a compromise that re-balances risk and benefit. [[User:Ttenbergen|Ttenbergen]] 01:19, 3 December 2025 (CST)
+* I heard nothing from the collectors about errors in sending since we started this new schedule.  If they work from home, can we allow them to send?  They can send early or after 04:30 PM.  [[User:PTorres|PTorres]] 14:27, 3 December 2025 (CST)
+** Open to it. If things work fine now, changing process may break them again. [[User:Ttenbergen|Ttenbergen]] 11:50, 17 December 2025 (CST)
+}}
 == Ongoing preparation during collection ==