The InPractice flow
InPractice reads the data already created inside the clinic system of record, protects it, structures it and turns it into a continuously updated evidence graph.
Start to continuous evidence
Scroll through the deployment path from the clinic's current EMR to a governed cohort that updates every week.
The source stays put
InPractice is not an EMR and is not a system of record. The clinic keeps its existing workflows, software and operating rhythm. There is no ERP-style migration and no clinic-wide change-management program.
Secure connection
A lightweight agent can read the data as it already exists in another EMR. Clinics using inPractice EMR can connect the evidence pipeline natively. Both paths are scoped to approved data and designed to avoid interrupting patient care.
Clinical pipeline
The initial cohort is de-identified, harmonized across formats and units, then mapped into the event-based InPractice ontology. Encounters, treatments, observations, images and outcomes become linked research signals.
Vision pipeline
Computer vision performs feature extraction, quality assessment, de-identification when required and structured analysis. This work runs alongside the clinical pipeline rather than waiting for it to finish.
Evidence layer
Clinical events and image-derived features resolve into one governed graph. Researchers can form cohorts around treatment, anatomy, device, product, observation and outcome without exposing direct patient identifiers.
Ongoing rhythm
After the initial load, the pipeline handles new or modified records and newly added images. The work becomes incremental, faster and aligned with the clinic's normal operating cadence.
Parallel by design
Structured records and clinical images move at the same time, then meet inside the ontology.
Clinical records
24–48 hours
Approximately 30,000 patients
Clinical images
24–72 hours
Approximately 100,000 images
Timing note: these ranges describe a best-case scenario. Actual duration depends on EMR access, data quality, governance review, data volume and available CPU or GPU resources.
After the initial load
Weekly updates only process new or modified records. Newly added images follow the same incremental pattern.
LLMs, computer use and computer vision are also making migrations between systems of record easier. That progress is useful context, but it is not a prerequisite for InPractice because the clinic does not need to migrate.
1–2 hours
New and modified records only
Minutes to hours
Only newly added images
Inside the evidence graph
Illustrative data · No PHIThis illustrative graph follows invented records through encounters, interventions, anatomy, image sets and observations. Choose a pathway to see how the ontology creates research context without using real patient data.
Illustrative graph overview
All identifiers, treatments and outcomes shown here are invented for demonstration. They do not represent real patients or clinical claims.
The result
Without replacing the EMR. Without changing how the clinic delivers care.