Network
Plan network and exchange access for cross-organization records.
Network connections are used when your product can request records through an exchange network. This setup is different from turning on a single EHR source. It depends on the network, permitted purpose, patient matching requirements, and the relationship your organization has to the patient or provider.
Open Connections in the dashboard, then review the providers under Network.
What the page shows
Network provider tiles show which exchange paths are available for the workspace and whether setup is self-serve, managed by Medblocks, or not yet configurable in the dashboard.
For managed network setup, Medblocks will confirm the exchange path, permitted purpose, identifiers required for patient matching, environment, and operational workflow before enabling the connection.
Because network access can reach across organizations, the setup usually needs more context than a client ID. Bring the use case, who is requesting records, why the request is permitted, what data you need, and where the records should go after retrieval.
What to prepare
Before network setup, gather:
- The clinical or operational use case.
- The organization making the request.
- The permitted purpose for exchange.
- Patient identifiers available at request time.
- The downstream destination or workflow that receives the records.
Medblocks uses this information to map the use case to the right network path and decide what needs to be configured in the workspace.
How it relates to other patterns
Network access complements the other connection types. Patient Access is still the fastest way for a patient-facing app to let people connect their own records. Backend access is still the right fit for organization-approved server-to-server sync. Network access is for cross-organization retrieval when the relationship and permitted purpose support it.
Not sure if this fits you?
Tell us what you're building and we'll show you exactly what you can integrate.