Create a patient session
Pick who renders connection search. Let Medblocks host the page, or build it into your own UI.
To pull a patient’s records, you first need them to sign in to their hospital’s patient portal, such as MyChart, and approve access for your app. That sign-in is the authorization step. There are two ways to put it in front of the patient. You can let Medblocks host the page, or build it into your own UI and send the patient straight to the hospital they chose.
Both end the same way. The patient runs through the same authorization, you get back the same patient session, and you read the same connection result. The only thing that differs is who renders connection search, where the patient finds and selects the hospital or clinic whose records you want to pull.
Medblocks-hosted page
Send the patient to a prebuilt page Medblocks hosts. They find their connection and approve there. The least code.
Your own UI
Build connection search into your own app with the SDK, then send the patient straight to their portal. Full control of UX and branding.
How to choose
The split comes down to three things, who renders connection search, how much control you have over how it looks and feels, and how much you build.
| Medblocks-hosted page | Your own UI | |
|---|---|---|
| Who renders connection search | Medblocks, on the page you redirect to | You, inside your app |
| UX and branding control | The page is themed to your brand, but the layout and copy are Medblocks’ | Full control. The search is part of your product |
| What you build | A redirect. Your server starts the session, then you send the patient to the url you get back | Search on top of the connection catalog, plus the redirect once the patient picks |
With the Medblocks-hosted page, your app does not need to know which connection the patient uses, and you build no search UI. The patient searches the catalog, picks a connection, and approves, all on the hosted page. That is the fastest way to launch.
With your own UI, you search the connection catalog yourself (see Find connections), show the results however you like, and pass the connection the patient picked into the session. The patient lands on their portal login directly, having never left your design.
Reach for the Medblocks-hosted page when you want the fastest launch and are happy to let Medblocks render connection search. Reach for your own UI when picking a connection is part of your product, like an intake or trial-matching flow where the choice carries its own context, or when you need full control of the experience.
You are not locked in. You can use both in the same product, for example offering your own search and falling back to the hosted page when a patient cannot find their hospital.