Overview

Put your app inside the EHR with CDS Hooks and SMART App Launch.

These Clinician Workflow docs are a work in progress. Use them as orientation while we expand the implementation guides.

Clinician workflow integrations put your product inside the place where clinicians already work. Instead of asking a provider to leave the EHR, search for the patient again, and copy context into another tool, Medblocks helps launch your app with the chart context already attached.

This surface is unlocked by an organizational relationship. The health system or clinic chooses to make your app available to its clinicians, and the EHR launch gives you the patient, encounter, user, and organization context your workflow needs.

What you can build

Use clinician workflow when your product needs to appear during care delivery:

  • A full embedded app launched from the patient’s chart.
  • A decision-support card shown at a specific point in the workflow.
  • A chart-aware experience that opens with the right patient already selected.
  • A handoff from the EHR into your application without asking the clinician to repeat context.

Medblocks focuses on the launch, context, authorization, and downstream data layer so your app can focus on the clinical experience.

Two common patterns

Configure the connection

Clinician workflow setup starts in your workspace’s Connections area. For Epic, Medblocks gives you the launch URLs, callback URLs, CDS Hooks discovery URL, and credential settings you need to share with the EHR administrator.

Configure Clinical Workflows

Not sure if this fits you?

Tell us what you're building and we'll show you exactly what you can integrate.

Book a call

See also