The InPractice flow

From practiceto protectedevidence.

Connect the records and images you already create. InPractice protects and links them into an evidence graph, while your EMR stays the source of truth.

Your EMR. Your workflow. Your control.

The evidence pathwayIllustrative model

Two paths. One protected flow. Clinical records and images are processed in parallel, with identity protection and structured context.

01Your existing system

02Two parallel pipelines

03One evidence graph

Start to continuous evidence

One connection.Six clear stages.

Scroll through the deployment path from the clinic's current EMR to a governed cohort that updates every week.

01

The source stays put

Keep the clinic system of record exactly where it is.

The evidence layer connects to the clinic's existing 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.

0systems replaced
02

Secure connection

Connect securely to the systems you already use.

A lightweight, on-premise agent reads approved data from the clinic's existing EMR. The connection is read-only and designed to work alongside established workflows without interrupting patient care.

Day 0connection begins
03

Clinical pipeline

Remove identity, normalize records and map the ontology.

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.

24–48hinitial clinical cohort
04

Vision pipeline

Analyze the image library in parallel.

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.

24–72hinitial image library
05

Evidence layer

Ingest a connected, research-ready cohort.

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.

< 1 weekrealistic deployment target
06

Ongoing rhythm

Process only what changed each week.

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.

1–2hweekly clinical update

Parallel by design

Two pipelines. One evidence layer.

Structured records and clinical images move at the same time, then meet inside the ontology.

Clinical records

24–48 hours

Approximately 30,000 patients

  • Identity removed
  • Formats and units normalized
  • Events mapped to ontology
  • Initial cohort ingested

Clinical images

24–72 hours

Approximately 100,000 images

  • Quality assessed
  • Features extracted
  • Identity removed if required
  • Structured analysis linked

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

The heavy lift happens once.

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

Weekly clinical update

New and modified records only

Minutes to hours

Weekly image update

Only newly added images

Continuous evidence

The cohort grows while the clinic keeps caring for patients.

Inside the evidence graph

Every signalhas context.

A treatment is one part of the story. Explore how records, anatomy, observations and images connect to give it context.

Three illustrative pathways. One connected model.

How do clinical signals connect?

Select a node to explore

Three invented pathways link records, encounters, treatments, anatomy, observations and images through one shared graph. Each connection links two records; it does not establish a clinical effect. Select any node to read its facts and its incoming and outgoing relationships.

Record relationshipShared providerSelected node

Illustrative examples · No real patient data

All identifiers, treatments and observations are invented. Connections show record relationships, not clinical results or evidence of treatment effectiveness.

07 / The result

Existing data becomes evidence the field can use.

Without replacing the EMR. Without changing how the clinic delivers care.

Source
Existing clinic EMR
Change
No workflow replacement
Output
Protected, research-ready evidence