Security & trust
Built for regulated records.
Two identification components for every session, WebAuthn-signed signature manifests, an append-only hash-chained ledger, and tenancy that keeps your data yours.
Multi-factor by default
Password plus an authenticator app (TOTP) or a security key / passkey (WebAuthn). A session that has not verified its second factor can do nothing but enrol one. 21 CFR 11.200(a).
Signature ceremonies
Medica shows you the signature manifest — printed name, register entry, meaning, document, revision, content digest — and your authenticator signs the manifest digest. Nothing else is signed; the signature is linked to the record and cannot be moved (21 CFR 11.50, 11.70).
Evidence ledger
Every decision, signature and refusal is a row with a hash chained to the previous one. Rows are never edited or deleted; corrections are new rows. The head hash is on screen and in every export (21 CFR 11.10(e)).
Tenant isolation
Each organisation is a separate tenant. Switching organisation opens a new session; roles are per organisation; nothing crosses.
Repository access
Controlled documents live in a PostDocs repository you own. Access is by per-user SSH keys you register and revoke in Medica; the web tier holds no credential.
Honest degradation
When a dependency is slow or down, Medica says so in words — serving a previously retrieved value, degrading a result or queueing a request — and records the posture. A spinner that lies is a defect.
Assist boundaries
Medica Assist drafts, cites and checks. It cannot classify, confirm, sign, release or file. Machine-written text is labelled until a person accepts it, and the acceptance is a ledger row.
Delivery model
Medica is proprietary software delivered as a cloud service or as an owner-operated instance. Third-party tools are reached as services over the network, never bundled.