Developers
V1MeClinicalPractitioner

Your currently verified practitioner identity, or null

Only the signed-in user's active, manually verified profile with valid credentials is returned. Registration does not establish verification. This response enables practitioner tools; each subsequent operation independently checks verification and patient approval.

GET
/v1/me/clinical/practitioner

Authorization

bearer
AuthorizationBearer <token>

In: header

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/me/clinical/practitioner"
{  "practitioner": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "name": "string",    "licenseAuthority": "string",    "licenseNumber": "string",    "specialistRegistration": "string",    "specialty": "string",    "organization": "string",    "verifiedAt": "2019-08-24T14:15:22Z",    "verificationValidUntil": "2019-08-24T14:15:22Z"  }}

Revoke clinical access POST

Previous Page

Issue your one-use five-minute clinical QR token POST

The token contains no health data and does not grant access. Encode only this opaque token in the QR. Send it in the claim POST body, never in a URL or analytics. A practitioner claim still requires your approval.