Page
ECW Data Store Findings
Purpose: Establish the verified repository, source path, execution model, and current readiness for the eCW Data Store workflow.
Verified Repository
The definitive repository is ecw-report-download, staged on this VM at /mnt/data1tb/mmelencio/ecw-report-download. It is the only Andalus Punongbayan contribution identified with the exact ECW Data Store destination identifier.
Fresh ECW Source
The Google Drive workflow does not query an eCW database or API directly. It retrieves eCW-generated report-delivery emails, matches exact configured report subjects, opens the delivered report links through browser automation, authenticates to eCW, and downloads the resulting source artifacts.
- Delivery source: eCW report emails from the configured report sender to the delegated data-science mailbox.
- Freshness rule: the current Google workflow searches the most recent delivery window and requires an exact report subject match.
- Retrieval method: browser automation opens the eCW report link and downloads the current generated file.
Pipeline and Destinations
- Find the exact eCW report-delivery email.
- Retrieve the report link and download the fresh source artifact.
- Retain the artifact for the current workflow run.
- Publish it to the selected governed destination.
Original destination: the finance workflow updates or creates same-name files in the ECW Data Store Google Drive folder.
Local-only destination: the updated workflow can retain current-run files on this VM at /mnt/data1tb/mmelencio/ecw-report-download/output/2026-q3-q4/ without contacting Google Drive. It does not sweep in stale files left in the temporary download directory.
Separate Azure variant: an Outlook-to-SharePoint version exists in the repository. It is a distinct destination path and is not the Google Drive Data Store workflow.
2026 Q3–Q4 Readiness
The catalog now includes the expected eCW delivery subjects for:
361.03 - Payments at Claim Level yr 2026 Q3-Q4371.03 - Payments at CPT Level yr 2026 Q3-Q4
These entries do not manufacture future events. They become retrievable only when eCW has generated and delivered the matching report. Q3 output can reflect source data available as of the run date. Q4 data cannot be truthfully created until the underlying eCW events and report delivery exist.
VM Readiness Findings
The repository contains a credential template, but this VM does not currently contain active values for the Google service-account payload or the eCW automation username/password. The legacy protected credential files expected by the older code are also absent. No active eCW scheduler or credential-reference service was found on this VM.
The safe preflight is operational and intentionally performs no download, upload, overwrite, or deletion:
python main2.py --period 2026-q3-q4 --dry-run
Once the source credentials are injected, this command verifies whether the current eCW delivery emails are available. The local-only retrieval command is:
python main2.py --period 2026-q3-q4 --local-only
Likely External Credential Location
Based on the repository design, the missing operational secrets are likely managed outside this VM, potentially in EHRFlow, an enterprise secret vault, protected deployment variables, or the original automation host. This is an informed operational inference, not a confirmed EHRFlow integration.
The required controlled inputs are a delegated Google service-account payload for delivery-mail access and an authorized eCW automation account for report download. The original Google Drive destination additionally uses the delegated service account for Drive access. No credential values are stored on this page.
Recommended Next Action
Provide the secrets through the organization’s approved secret-management path, run the read-only preflight, confirm exact eCW report availability, then run the local-only retrieval. Do not create placeholder Q4 clinical or financial event data.