Overview
Reach a patient's records across organizations through the national networks.
Network integrations are for reaching records across organizations when your product has the right clinical relationship and permitted purpose. Instead of integrating one hospital at a time, exchange networks can help discover and retrieve records from many participating organizations.
This is not a shortcut around consent, treatment relationships, or policy. It is a different integration surface for products that are allowed to request records through networks such as CommonWell, Carequality, TEFCA-aligned exchange, or other regional and national connectivity paths.
When network access helps
Network access is useful when the record you need is not limited to one known source:
- A care team needs outside records before a visit.
- A specialty service needs longitudinal history across prior sites of care.
- A clinical workflow depends on documents, encounters, medications, labs, or conditions from multiple organizations.
- Your product has a treatment or operational context where network exchange is permitted.
Patient access and backend access are still valuable even when you add network access. Patient access is often fastest for consumer-facing products. Backend access is better for organization-scoped sync. Network access fills in the cross-organization record when the relationship supports it.
How Medblocks fits
Medblocks helps map your use case to the right exchange path, configure the network connection, monitor retrieval, and normalize the records that come back alongside data from your other sources.
Because network access depends heavily on your product, relationship, and permitted purpose, setup is usually a conversation rather than a purely self-serve toggle.
Configure the connection
Use Configure Network to understand what belongs in the workspace configuration and when to reach out.
Not sure if this fits you?
Tell us what you're building and we'll show you exactly what you can integrate.