Find a patient by MRN
Resolve your own medical record number to a medos patient id.
GET /v1/patients/search-by-mrnThe lookup most hospital systems actually want — you already have a medical record
number, and need medos's patientId for it.
API-key only (a widget session is refused) and entitlement-gated on devapi_patients_lookup_mrn.
Query parameters
| Name | Required | Description |
|---|---|---|
mrn | Yes | The medical record number as medos stores it. |
Try it
/v1/patients/search-by-mrnAPI key onlydevapi_patients_lookup_mrnThe normal way an HMS resolves its own record to a medos patient id.
Query
GET /v1/patients/search-by-mrnhttps://api.medos.oneUse a dedicated test key, and put your browser's address on its allowlist
A Developer API key authenticates on its own, so it only works from the addresses registered against it — and this page calls from your browser, not your servers. Unless your own public address is on the list you get a 403 naming it, which is the allowlist doing its job. Your browser may also reach us over IPv6 even when your server does not, so the address in the error is often not the one you expected. The key here is kept in memory only and never written to storage, but create a test key for it and deactivate that key when you are done.
Request
curl -sG "https://api.medos.one/v1/patients/search-by-mrn" \
-H "x-api-key: $MEDOS_API_KEY" \
--data-urlencode "mrn=MRN-0774"This is not the same as the widget's search-by-phone: that one scopes to a phone the patient proved they own, and needs the OTP gate open. This is a staff-side read over the workspace, gated by your plan instead of by patient consent.
Common failures
| Status | Cause |
|---|---|
403 with requiredFeature | Not entitled to this operation. |
403 "only available to Developer API keys" | A widget session token was used. Send x-api-key. |