MDClarity · ClarityFlow · the ingest side
The front door
The same Flow spine runs behind every pipeline — what differs at the front is the source system (which EHR) and the transport (how its data physically arrives). This is the ingest axis: slice by how a feed comes in, not by customer. Source systems are detected name-level (from job / sub-job names), so a feed whose pipeline doesn't name its EHR shows as unnamed; transport comes from the actual ingest steps.
the feeds · 22 pipelines
How each feed arrives
Flow pipelines grouped by transport. Each links to its task tree; source-system tags link to that EHR's provenance. This answers “who ingests over HL7 v2 / FHIR / SFTP / Snowflake.”
| EugeneGIFlow-MM-HL7-Processing | ModMed | every 30 min |
| EugeneGIHL7-Processing-Nightly | ModMed | daily 19:34 |
| OrthoAllianceFlow-34792-Processing | unnamed | every 5 min |
| RIAFlow-HL7-Processing | unnamed | every 1 min |
| RIAFlow-HL7-Processing-AutoSendLettersForFutureVisits | unnamed | daily 19:01 |
| SeaRadDaily-Visit-Processing-HL7 | unnamed | every 10 min |
| StrideCareFlow-HL7-Processing | unnamed | every 10 min |
| SWOrofacialFlow-HL7-Processing | unnamed | every 10 min |
| HeatonEyeDaily-Processing | NextGen | daily 08:30 |
| MNEyeDaily-Processing-Visits | unnamed | chained |
| OneGIFlow-ECW-Processing | eClinicalWorks | daily 23:00 |
| OneGIFlow-MM-Processing | unnamed | daily 03:00 |
| PAADaily-Processing | Phygen | daily 11:15 |
| PAADaily-Processing-PAAMobile | Phygen | daily 14:30 |
| PPRMDaily-Visit-Processing | NextGen | daily 05:00 |
| SeaRadDaily-Visit-Processing | unnamed | daily 22:15 |
| SSRDaily-Processing | unnamed | every 30 min |
| SunLifeDaily-Visits-Processing | eClinicalWorks | daily 10:30 |
| WildfloweroffFlow-Processing | unnamed | every 10 min |
| MannEyeoffFlow-FHIR-Processing | unnamed | every 10 min |
| NWDermFHIR-Processing | unnamed | every 2 min |
| SeaRadDaily-Processing-Eligibility | unnamed | monthly 00:30 |
source systems · 4
The EHRs behind the feeds
Every upstream system named in a Flow pipeline. Each opens its provenance — the EHR family, how it's delivered, and the migration gotchas.
Two transports across customers: SFTP delimited files (OneGI, SunLife) and direct SQL Server queries (Partnercare).
Multiple transports across the base: CSV-over-SFTP (Wildflower), HL7 v2 files (EugeneGI), and the off-repo Flow-MM API (OneGI).
File schemas live in an app-DB data_file_spec table — a migration needs that table or a code-defined equivalent.