Retrieve an EHR launch context
Resolve the mb_launch handle (appended to your app's launch URL after an EHR launch) into the patient / encounter / practitioner / EHR the app was launched in.
Authorization
BearerAuth AuthorizationBearer <token>
Medblocks API key for server-side requests.
In: header
Path Parameters
id*string
The mb_launch handle appended to your app's launch URL by Connect after an EHR launch.
Format
uuidHeader Parameters
Version?string
Date-pinned API version. If omitted, Medblocks uses the version pinned on your API key.
Response Body
application/json
application/json
curl -X GET "https://example.com/launch-contexts/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "Version: 2026-04-25"{ "id": "9c9b6f7a-8e4f-4a3b-9c1e-6f3a2d8b7c4d", "resource_type": "launch_context", "status": "ready", "patient": "Patient/erXuFYUfucBZaryVksYEcMg3", "encounter": "Encounter/eMHbz3rPbqUjMqpUgVrhwgB3", "fhir_user": "Practitioner/eM5CWtq15N0WJeuCet5bJlQ3", "scope": "launch openid fhirUser patient/Patient.read", "fhir_source": "fhirsrc_02Zh2bnvRoWQJYgOAkI0Twcc", "fhir_base_url": "https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4", "created_at": "2026-06-09T14:30:00.000Z"}{ "error": { "type": "authentication_error", "code": "invalid_api_key", "message": "API key invalid", "param": null, "doc_url": "https://docs.medblocks.com/errors/invalid_api_key", "request_id": "9c9b6f7a-8e4f-4a3b-9c1e-6f3a2d8b7c4d" }}Non-2xx responses use the standard API error envelope. Log
error.code and error.request_id for support.