Data syncs
Data syncs are the background processes that keep MedFlow’s clinical picture current. They run on a schedule, pull data in from your connected systems, and apply the tags that search and queries rely on. Nothing here is fired by a single API call. It is the steady, behind-the-scenes work that keeps Find accurate.
What they do
Section titled “What they do”Each time a data sync runs, it does two things:
- Sync data. It brings the latest clinical and operational data from a data source into MedFlow.
- Apply tags. Once the data is in, it applies the standard tags that describe each patient and pathway, so queries can select the right cohorts.
Schedules
Section titled “Schedules”Syncs run at whatever cadence a source and its data need:
| Cadence | Typical use |
|---|---|
| Quarter-hourly | Time-sensitive activity, such as new results or admissions |
| Hourly | Most operational data |
| Daily or nightly | Full refreshes and heavier syncs |
A search trigger can then rerun its query on its own schedule, knowing the data underneath is current.
How syncing works
Section titled “How syncing works”Wherever a system supports it, MedFlow syncs clinical data using FHIR Bulk Export, the HL7 standard for exporting large sets of FHIR resources. It is the most efficient and portable way to keep a full clinical picture in sync.
Not every source speaks FHIR. For proprietary or non-standard data sources, MedFlow converts everything to FHIR on the way in. Normalizing to one standard means tagging, search, and pathways behave the same way no matter where the data came from, so there is not a different shape to reason about for every vendor.
How it fits
Section titled “How it fits”- Data sources are the connectors themselves: the catalog entries that define what MedFlow can sync from.
- Data syncs are the scheduled processes that run those syncs and apply tags.
- The result feeds Find: current, tagged data that search, queries, and search triggers act on.