How Medblocks works
Source to connection to background pull to the systems where your team works.
Medblocks is the integration layer between your product and the healthcare systems that hold patient data. It helps you reach the systems your relationship allows, complete authorization, pull records in the background, and send those records to the systems where your team works.
The path is simple.
- A source is a system you can reach, such as an EHR, payer, network, or wearable.
- A connection is the authorized link between a patient, organization, or workflow and that source.
- A pull brings records from the source into Medblocks.
- Your app receives operational updates through webhooks and dashboard history.
- Records leave Medblocks through exports, API reads, or downstream workflows.
A source and a connection are the two core ideas. Sources and connections defines both in full, including the source catalog, what Medblocks handles on its side, and the connection lifecycle. Each pattern is unlocked by a real relationship you already have, not one enterprise contract that bundles every surface.
Your App
You can use Medblocks in code or from the dashboard.
- Pick the integration pattern that matches your relationship. Start with Patient access to let patients connect their own records, launch inside the EHR with Clinician workflow, sync server to server with Backend, or reach records across Network.
- Use Data out to decide whether records should arrive through exports, API reads, or events.
- Use Pull monitoring and Auth event history when you need to operate the connection after authorization.
- Use Workspace when you are ready to create an organization and API key.