Data Transfer (Export API)

Controlled, read-only data transfer. Only the platform operator (SuperUser) defines a connection + key for a clinic; the key pulls that clinic's data from the selected "VEM" (Minimum Data Model view) datasets. There is no cross-tenant access. It complies with the data portability obligation (Regulation No. 39682, Art. 14).

How does it work?

Authentication

Every request must carry an export key. Two methods are supported; the key is stored only as a SHA-256 hash.

Authorization: Bearer udx_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
— or —X-Export-Key: udx_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Endpoints

Example Usage

Pull patients (VEM)

curl https://udentiva.com/export/v1/patients?limit=1000 \
  -H "Authorization: Bearer udx_xxxxxxxx"

HTTP/1.1 200 OK
{
  "dataset": "patients",
  "count": 1000,
  "limit": 1000,
  "offset": 0,
  "rows": [ { "patient_id": "...", "tenant_id": "...", "first_name": "..." } ]
}

VEM View — View Schemas

Every exportable dataset is a fixed-column VEM View (Minimum Data Model view). Below you'll find each set's full column schema, data types and (where applicable) the corresponding Ministry of Health VEM field. Monetary fields are returned as decimal (numeric), identifiers as uuid, and dates as ISO-8601 (timestamptz).

Security Model

Other Resources