Clinics
Clinic API, EHR export and AI assistants
Connect ReadySeen to your EHR, intake system or AI assistant, without giving up end-to-end encryption.
ReadySeen for Clinics includes an API, so the briefs patients send you can flow into the systems you already use. Brief contents stay end-to-end encrypted: the API hands out ciphertext only, and ReadySeen Connect decrypts it on your own computer or server with your vault passphrase. The passphrase and the readable briefs never reach us.
1. Create a key
Dashboard → Settings → API keys (owners only). Name the key after where it's used. A key has the briefs:read scope, and optionally briefs:write to mark briefs seen. It is shown once; we store only a fingerprint. Revoke a key at any time, and it stops working at once. Every brief opened with a key appears in your Activity log.
2. The API
Base URL https://readyseen.com/api/v1. Send Authorization: Bearer rs_live_…. JSON in and out. Limit: 120 requests a minute per key.
| Method and path | Scope | Returns |
|---|---|---|
GET /clinic | briefs:read | Your clinic, the key's scopes, and your vault's public parameters (locked with your passphrase) |
GET /briefs?since=<ms>&unseen=1 | briefs:read | Briefs from the last 30 days: id, label, times, seen and expired status. No health information |
GET /briefs/<id> | briefs:read | One brief as ciphertext plus its wrapped key. Needs an active plan or pilot. Logged |
PATCH /briefs/<id> with {"seen": true} | briefs:write | Marks it seen or unseen in your inbox |
3. ReadySeen Connect (the connector)
One file, no installs beyond Node.js 20+: download readyseen-connect.mjs. Set READYSEEN_API_KEY and READYSEEN_VAULT_PASSPHRASE in its environment, then:
node readyseen-connect.mjs checktests the key and the passphrase.node readyseen-connect.mjs list --unseenlists new briefs.node readyseen-connect.mjs read <id> --format text(orjson, orfhir) prints one brief.node readyseen-connect.mjs export --out <folder> --format fhir --mark-seenwrites each new brief as a FHIR R4 Bundle (a QuestionnaireResponse with the patient's answers and warning signs, plus one Media resource per photo), ready for your EHR's import or interface engine.
4. AI assistants (MCP)
node readyseen-connect.mjs mcp runs a Model Context Protocol server, so an AI assistant can list new briefs, read them, summarise them for the clinician, and mark them seen. Add it to your assistant's MCP settings as a command with those two environment variables. Tools: clinic_info, list_briefs, read_brief (text, JSON or FHIR, photos optional) and mark_brief_seen.
Decrypted briefs are protected health information. Connect them only to systems and AI services covered by your business associate agreements, or to an AI model that runs on your own hardware. LIKE A KING INC. can install one for you (see below).
5. Need more? We build it
LIKE A KING INC., the company behind ReadySeen, builds for clinics and hospitals: EHR and FHIR/HL7 interfaces, a private AI front-desk and operations assistant that runs on hardware in your building, new websites and patient apps, and the infrastructure under them. Tell us what you need.